[jdev] Proposal for a solution to transport rosters

Justin Karneges justin-keyword-jabber.093179 at affinix.com
Sat Sep 4 14:15:17 CDT 2004

On Saturday 04 September 2004 2:05 am, Bart van Bragt wrote:
> Justin Karneges wrote:
> > While this would certainly work, I think a server-side extension would be
> > better.
> It would be great if this could be solved on the server side but I don't
> really see that happening within now and a year, especially with the
> current state of the jabberd2 project. Furthermore that will give an
> inconsistent userexperience. Some users will be able to add transports
> without a hassle (up to date server) and others (with the same client)
> will have to click on silly buttons for half an hour to be able to talk
> to their existing contacts.

In each solution, it's going to take either an upgrade of clients and 
transports, or an upgrade of servers and transports.  Normally anything that 
requires a server upgrade is considered difficult (which is unfortunate, 
because sometimes it is the right way), however in this case it might 
actually be easier, since the admin must already go out of his way on the 
server-side because he has to upgrade his transports.

See what I mean?  It's not something that just the clients can solve this 
time.  It's msn-t also, which is a server component.  And those servers that 
don't upgrade their msn-t will be giving inconsistent user experiences 
anyway, regardless of which solution we go with.  This is one of those rare 
situations where upgrading the server side is likely the easier path.


More information about the JDev mailing list