Safa wrote:
Hi all, I am working on this issue and have some questions. Can the xmpp:restart body be non-empty?
I'm not sure. I would consider Ian Paterson to be the canonical authority regarding BOSH, except that it seems he has dropped off the face of the earth. Therefore I think it's up to us to figure out what's right and what's wrong.
But to answer your question, I think not that behavior is potentially problematic, because stream restart means "consider anything I send after this to be null and void, since the old stream is gone". I suppose the connection manager could cache the <body/> and send it over the new stream, but I think it's better not to send anything until you receive notification that the new stream is up and running.
For example, emite sends the bind request within the body containing xmpp:restart.
I don't think that's right, but I can't say so with 100% confidence.
If the answer to the previous question is yes, would it be correct to include both stream features and the bind result in the same response body?
If so, yes. How many roundtrips / bytes does this save? Is it worth the bother? /psa
smime.p7s
Description: S/MIME Cryptographic Signature
