[ejabberd] pushing rosteritems to "own" resource

Peter Saint-Andre stpeter at stpeter.im
Mon Aug 24 19:49:40 MSD 2009


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 8/24/09 6:03 AM, Stephan Maihöfer wrote:
> hi,
> 
> i am encountering different behaviours for ejabberds
> roster-push after altering rosteritems (renaming for example).
> 
> both servers are ejabberd-2.1.0-alpha but behave differently
> somehow. the one server pushes the item to the resource
> that initiated the change, on the other server there is only
> the result sent, nothing else.
> 
> is this intended behaviour? it seems that the standard says
> "push to ALL connected resources". did i read that wrong?
> where in the code did that change (if at all).

Push to all interested resources is indeed the rule.

Peter

- --
Peter Saint-Andre
https://stpeter.im/


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkqStpQACgkQNL8k5A2w/vyGAgCglldln9DLrsWrjTuH07333Ivv
PQ4An0X3FZ+KYGYUZHqFbUmNbboNYNQ/
=gNIe
-----END PGP SIGNATURE-----


More information about the ejabberd mailing list