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
&& is the header, just two ampersands, that indicates this is a fragmented message
XXX is the message id: every fragement of each unique message has the same ID
T is the kind of messge: 'A' is a fragment, 'B' is the last fragment, 'C' is "missing packets" and 'D' is ACK.
N is the fragment number
| is a pipe to indicate the end of the fragment number
msg is the base64 encoded message
| ends the message
When an application send an AO to Nuntium it must include "fragment=true" or "fragment=1" as a custom attribute for the message to be gzipped and fragmented. This results in an AO created for the message and AOs created for every fragment of the message as children of this main AO.
Original comment by Ary Borenszweig on 2014-01-16 14:55:18+00:00
Long messages with a fragment flag should be gzipped, encoded in b64 and fragmented
The text was updated successfully, but these errors were encountered: