[JDEV] Transports in jabber

[Thomas D. Charron]

  Do the the limitations you pointed out, the transport will need to have a means to create and manage user ID's.  Currenty, this is stored in the transport configuration data, due to the fact that we are currently looking at finalizing private storage of user data, including such things as AOL User ID and Password.  Once this happens, when the user attempts to send a message to AOL, the transport will query the AOL user info.  If not present, it will have some method for creating a new userID for that user, and set the data.  Once this happens, the user can freely talk back and forth between AOL users.  To the AOL user, he/she will have the AOL username.  The them, they are the same old person.  Keep in mind, this is a limitation of AOL's network namespace, not ours..

  If AOL indeed keeps it's 'promise to support open standards', then they will need to eventually comply with the draft IETF IMPP standards, which allow for an open namespace, versus a closed one, and things will be a whole lot simpler for us..

---
Thomas Charron

On Sat, 28 Aug 1999 17:35:27   Oleg Gordiychuk wrote:
>
>
>Hello All,
>
>I've read the documents on jabber.org and now have a question: how are you going
>to support "transparent" sending of instant messages to, say, AOL? If you want
>to send a message to an AOL user, you have to be registered on AOL server with
>some name. Of course, you can't register jabber users automatically once started
>to use jabber. Another option: you can use some fake names to access AOL
>community. But it may mean a lot of foreseeable problems. As I understand, this
>is one of the basic concepts of the project, and I did not find any explanation
>anywhere.
>
>Thanks,
>
>--- Oleg
>
>
>
>
>_______________________________________________
>jdev mailing list
>jdev at jabber.org
>http://mailman.jabber.org/listinfo/jdev
>


--== Sent via Deja.com http://www.deja.com/ ==--
Share what you know. Learn what you don't.