On Fri, Feb 25, 2011 at 9:49 AM, Michael McCarthy <michaelcmccar...@me.com> wrote: > Thanks Kevin. We do control both clients, and we actually do a similar thing > with roster invites (the other client listens and auto accepts the "to" > subscription). Presumably the to for that IQ would be their room JID, i.e. > jdev@jabber.org/Kevin which is available to you?
Right. /K > > On 25 Feb, 2011,at 09:20 AM, Kevin Smith <ke...@kismith.co.uk> wrote: > > On Fri, Feb 25, 2011 at 9:17 AM, Michael McCarthy > <michaelcmccar...@me.com> wrote: >> Sorry, I wasn't very explicit there, my mistake. This is within the >> context >> of an application we've written where users probably aren't aware they are >> using XMPP or what a JID is. But I like the pragmatism of the approach >> below >> : ) > > If you control the clients at both ends, you can have them respond to > e.g. <iq to=...><whatsyourjid xmlns="..."/></iq> and do the user-less > equivalent to Peter's suggestion. Understanding whatever privacy > issues this brings to your application. > > /K > _______________________________________________ JDev mailing list Info: http://mail.jabber.org/mailman/listinfo/jdev Unsubscribe: jdev-unsubscr...@jabber.org _______________________________________________
