<html><body><div>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? <br><br>On 25 Feb, 2011,at 09:20 AM, Kevin Smith <kevin@kismith.co.uk> wrote:<br><br></div><div><blockquote type="cite"><div class="msg-quote"><div class="_stretch">On Fri, Feb 25, 2011 at 9:17 AM, Michael McCarthy<br> <<a href="mailto:michaelcmccarthy@me.com" _mce_href="mailto:michaelcmccarthy@me.com">michaelcmccarthy@me.com</a>> wrote:<br> > Sorry, I wasn't very explicit there, my mistake. This is within the context<br> > of an application we've written where users probably aren't aware they are<br> > using XMPP or what a JID is. But I like the pragmatism of the approach below<br> > : )<br> <br> If you control the clients at both ends, you can have them respond to<br> e.g. <iq to=...><whatsyourjid xmlns="..."/></iq> and do the user-less<br> equivalent to Peter's suggestion. Understanding whatever privacy<br> issues this brings to your application.<br> <br> /K<br> </div></div></blockquote></div></body></html>