You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: standards/application/chat-framework.md
+7-5Lines changed: 7 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -40,13 +40,15 @@ Defining these 5 parameters allows for chat protocol implementations to be fully
40
40
41
41
### Delivery service
42
42
43
-
The service or method that distributes payloads to clients is called abstractly called a `Delivery Service` or `DS`.
43
+
A Delivery Service (DS) is the service or method that distributes payloads to clients. A DS accepts payloads with a delivery_address and delivers them to all subscribers of that delivery_address. Protocols use delivery_addresses to establish delivery contracts between senders and recipients. The mapping of delivery_addresses to DS-level concepts is implementation-specific.
44
44
45
-
- a DS MUST have a method for clients to subscribe to messages.
46
-
- a DS MAY NOT guarantee delivery of messages.
47
-
- a DS MAY NOT guarantee order of messages.
45
+
#### Requirements
46
+
47
+
- -A DS MUST provide a method for clients to subscribe to messages from a delivery_address
48
+
- Payloads sent to a delivery_address are delivered by a DS to all subscribers of that delivery_address
49
+
- A DS MAY NOT guarantee message delivery
50
+
- A DS MAY NOT guarantee message ordering
48
51
49
-
How protocols are mapped to DS level concepts is to be defined by implementors.
0 commit comments