the callbacks will be called in the order the messages were sent, assuming they're on the same NetStream. different NetStreams' data are sent on different flows, so the order between them may not be maintained.
Thank you Michael
Does this also mean that all messages are guaranteed to arrive? I saw that the NetStream class has a dataReliable property. Is it relevant for cirrus?
if dataReliable is true, then NetStream.send messages are sent with full reliability.
Could I take this opportunity to ask you if there are any plans to implement an option for messages to arrive out of order soon?
It's a huge flaw in the protocol that this currently isn't possible. In real time games when latency is very important, it's extremely frustrating to have messages sat waiting at the receiving clients end, unable to be processed because older, redundant messages must arrive first.
Please allow this to be turned off!