[ejabberd] in-order delivery
mickael.remond at process-one.net
Tue Mar 7 21:07:15 MSK 2006
Le 7 mars 06 à 17:56, Sergei Golovan a écrit :
> On Tue, Mar 07, 2006 at 04:45:35PM +0100, Mickael Remond wrote:
>> * Peter Saint-Andre <stpeter at jabber.org> [2006-03-06 13:49:52 -0700]:
>>> -----BEGIN PGP SIGNED MESSAGE-----
>>> Hash: SHA1
>>> It seems that ejabberd doesn't deliver stanzas in order. In
>>> I've had several people complain that at jabber.org their clients
>>> 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.
>> It is not really in-order delivery (order preservation of message).
>> However, I agree with your point. It considerably simplify client
>> development to make such hypothesis.
> I don't agree. At least in the example of roster and presence IMHO
> it's very
> simple to store all received roster items and presences
> independently and
> update visible roster on both types of events. (BTW, most clients
> that were
> written in jabberd 1.4 times (Tkabber, JAJC, Psi, whatever) work
> fine with
> ejabberd, so it's natural to do so.)
It depends in which technology you are developing the client. Clients
in Flash or mobile client have limited resources and it is wise to
limit when possible the array size you need to store, IMHO.
More information about the ejabberd