[jdev] discovery services

Justin Karneges justin-keyword-jabber.093179 at affinix.com
Tue Mar 22 23:31:05 CST 2005

On Tuesday 22 March 2005 05:31 pm, Julian Missig wrote:
> On 22 Mar 2005, at 20:00, Justin Karneges wrote:
> > 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.
> 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.

You make a good point, dialback is probably not needed.  Perhaps the login 
handshake can be done using SASL.  However, everything else in an ad-hoc 
setup is unavoidably more like s2s than c2s.  Here is what implementations 
need in addition to regular c2s:

 1) ability to handle incoming TCP connections
 2) ability to perform the XMPP stream handshake process in reverse
 3) stanzas need to indicate both the 'to' and the 'from' (since either 
workstation might have multiple users.  yes, I think we should be forward 
thinking here).

Hmm, have I described ad-hoc or s2s?  You can decide. :)


More information about the JDev mailing list