[ejabberd] pushing rosteritems to "own" resource
sma at turtle-entertainment.de
Tue Aug 25 12:16:05 MSD 2009
do you mean that ejabberd does this correctly at the moment and
that it is my fault somehow, or did you only mean that the
xmpp-rfc requires ejabberd to send to ALL resources, including
> -----Original Message-----
> From: ejabberd-bounces at jabber.ru
> [mailto:ejabberd-bounces at jabber.ru] On Behalf Of Peter Saint-Andre
> Sent: Monday, August 24, 2009 5:50 PM
> To: ejabberd at jabber.ru
> Subject: Re: [ejabberd] pushing rosteritems to "own" resource
> -----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 Saint-Andre
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.8 (Darwin)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
> -----END PGP SIGNATURE-----
> ejabberd mailing list
> ejabberd at jabber.ru
More information about the ejabberd