[ejabberd] pushing rosteritems to "own" resource

Stephan Maihöfer sma at turtle-entertainment.de
Mon Aug 24 16:03:27 MSD 2009


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).

greetings,
stephan


More information about the ejabberd mailing list