[jdev] discovery services

Julian Missig julian at jabber.org
Tue Mar 22 19:31:54 CST 2005

On 22 Mar 2005, at 20:00, Justin Karneges wrote:

> 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 user at workstation.
> 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.

Honestly, I prefer iChat's approach. Clients already have client  
libraries that speak the c2s protocol. You strip out some of the  
login/auth stuff and just use c2s to one another. That requires a lot  
less new implementation and allows for a lot more code re-use... at  
least the way Jabberoo was designed and how I imagine most libraries  
are designed.

Since it's local I don't really see a need for Dialback and its  
multiple socket connections and all sorts of other server pains that  
client developers haven't had to be exposed to yet.


More information about the JDev mailing list