[ejabberd] in-order delivery
pgmillard at gmail.com
Thu Mar 9 05:44:48 MSK 2006
The roster versus presence problem isn't nearly as bad as processing
jabber:iq:privacy packets. If a client sends an iq-set which enables a
privacy list, then I send some other packet, the iq-set for the
privacy list MUST be enabled before my second packet is processed.
This is one of the reasons that RFC says that an entity must *process*
the packets in order.
On 3/6/06, Peter Saint-Andre <stpeter at jabber.org> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> It seems that ejabberd doesn't deliver stanzas in order. In particular,
> I've had several people complain that at jabber.org their clients are
> receiving presence before the roster. It's possible that this needs to
> be clearer in RFC 3921, but IMHO it is best to deliver presence only
> after delivering the roster.
More information about the ejabberd