Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fragment message #1

Open
waj opened this issue Sep 3, 2014 · 1 comment
Open

Fragment message #1

waj opened this issue Sep 3, 2014 · 1 comment
Labels

Comments

@waj
Copy link
Contributor

waj commented Sep 3, 2014

Long messages with a fragment flag should be gzipped, encoded in b64 and fragmented


@waj
Copy link
Contributor Author

waj commented Sep 3, 2014

The format of a fragmented message is:

&&XXXTN|msg|

where:

  • && 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

@waj waj added the task label Sep 3, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant