[jdev] send message to user's contacts

[Daniel Dormont]

Thanks Dave.

I haven't tested this particular feature yet, but ejabberd does implement
XEP-0133 so I imagine being able to fetch the roster as admin is something
I could do. I guess I was just hoping to do the routing server side to
reduce traffic from my client.

If it were supported, how would it work from the publishing side? I admit
I'm pretty new to pubsub generally, so I'm still a little unclear. But from
what I understand, the publisher normally just passes a NodeId that is
semantically meaningful (in this case for geolocation) and the server
recognizes it as a PEP event and handles it accordingly. So what would the
admin do to say that actually this is a PEP event on behalf of a certain
user?

dan

On Wed, Aug 7, 2013 at 5:36 AM, Dave Cridland <dave at cridland.net> wrote:

> If it's location data (like XEP-0080) then PEP is exactly right.
>
> The only slight problem is that although PEP (XEP-0163) certainly doesn't
> preclude the kind of admin access you're after, the vast majority of PEP
> implementations don't seem to support it, and instead do a minimal (and in
> some cases, below minimal) implementation of XEP-0060 as required to
> support only the specific cases outlined in XEP-0163.
>
> I suspect ejabberd is one such case. I know Isode's M-Link server does (or
> did) support these cases in its PEP implementation because I wrote that
> support when I worked for Isode, and it wouldn't surprise me at all if
> Prosody also handled them (but I don't know).
>
> Your other alternative is to read off the roster for the user (as admin),
> and manually broadcast; this won't be as good, and again requires either
> support for an unusual case (Isode's M-Link, again, supports admin users
> making standard roster get requests to other jids, or did when I last
> looked), or else using the server's own administrative API should it have
> one. I'm pretty sure both ejabberd and Prosody have some mechanism, in or
> out of XMPP, for reading a user's roster.
> Dave.
>
> _______________________________________________
> JDev mailing list
> Info: http://mail.jabber.org/mailman/listinfo/jdev
> Unsubscribe: JDev-unsubscribe at jabber.org
> _______________________________________________
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.jabber.org/jdev/attachments/20130807/30db221e/attachment.html>