On Tuesday 22 March 2005 04:40 pm, Julian Missig wrote: > For an official form of something like iChat Rendezvous, we'd need to > define what exactly an XMPP client<->client protocol should look > like, which pieces of XMPP are disallowed, and when TCP connections > should actually take place. All things which I was interested in > doing back when it looked like something I'd be adding to Gabber one > day, but which unfortunately I don't think I'll be implementing in > anything anytime soon...
Ignoring how iChat may or may not do it, I figure the most straightforward answer would be to have the clients perform the xmpp-core s2s protocol with each other. JIDs become [EMAIL PROTECTED] What we just need then is some document explaining the zeroconf process of locating local Jabber servers, both for xmpp-client and xmpp-server, and a way to query an xmpp-server for its users. The xmpp-server type could be either a "real" server (in the Jive sense), or an ad-hoc rendezvous-style workstation hosting a single user. To outsiders, it really makes no difference. Finally, although not strictly necessary, a nice iq protocol for "normal" Jabber clients to access the above features via an intermediate Jabber server would make it easier for existing clients to become ad-hoc aware. -Justin _______________________________________________ jdev mailing list jdev@jabber.org http://mail.jabber.org/mailman/listinfo/jdev
