[JDEV] Protocal Specifier on jabber addresses; creation of JUPLs

[Richard Dobson]

----- Original Message -----
From: "David Sutton" <dsutton at legend.co.uk>
To: <jdev at jabber.org>
Sent: Sunday, November 25, 2001 2:49 PM
Subject: Re: [JDEV] Protocal Specifier on jabber addresses; creation of
JUPLs


> Hello,
>
>   I can understand the idea which you are proposing, but it looks to me
> that it would be best inplemented
> on the client side, rather than server side. Let me explain:
>
>   In the example, it was shown that different jabber servers have
> different transport addresses, well the
> situation is more complex than that. There is little to stop me from
> registering with the msn.jabber.com
> transport from jabber.org. In that case, the msn.jabber.com address
> would work and the msn.jabber.org
> would not. In fact, this flexability has proven most useful in the whole
> AOL affair, meaning that a jabber
> user can try and find a transport on another server which will work for
> them.
>
>   With this in mind, it wouldn't be difficult for the client software
> translate the suggested scheme into the
> transport the user had registered with. I.e. msn:test at hotmail.com =>
> test%hotmail.com at registered.transport

Yes but to make sure it works with all clients it should really be a server
side thing, but thats a definate point that there needs to be a way to pick
which transport server you wish to use.

Now what about this, because the transport itself is already a part of the
roster the server will know which one you are using and can translate the
address itself, this also allows you to change transport servers by just
deleting the existing one from your roster and subscribing to another all
without having to rebuild your roster items that were on the old transport
server, the jabber server will just redirect the xml packets to the new
server automatically.

>   Extending this further, it could be made to popup a registration
> window to the nearest transport if you call
> a transport which you are nor registered to.
>
>   Another possibility would be allowing the user to register to the same
> transport on different servers, and
> the client keeps the rosters in sync. The generic address will then
> chose the best transport and send through
> that.

Would not work for AIM or MSN tho as as soon as you logged in another
session it would auto logout any previous ones.

> Just a few ideas.
>
> David