[JDEV] Best way to drive Jabber adoption?

[Steven Brown]

> -----Original Message-----
> From: jdev-admin at jabber.org [mailto:jdev-admin at jabber.org] On 
> Behalf Of Timothy Carpenter
> Sent: Saturday, June 14, 2003 2:19 AM
> To: jdev at jabber.org
> Subject: Re: [JDEV] Best way to drive Jabber adoption?

> To get around the CLIENT knowing many transports and many 
> clients having to do that, I suggest we have each desktop run 
> a small private SERVER that has all the transports.

One of the significant benefits of Jabber is that it is easily used by
thin clients, even unconnected polling clients with a bit of server
hacking (support for this should be built-in).  Requiring transports to
run client side would kill this, and be a huge portability mess.  What's
wrong with the current situation, other than the general buggyness of
the current transports?

> Client designers can then focus on look-and-feel, skins, 
> usability, thinness and robustness and forget about having to 
> handle multi-platform issues which, frankly, each client is 
> re-inventing the wheel in that regard.

All of the details of transports are abstracted away from the client.
If you know how to register for one, you know how to register for them
all.