[JDEV] Transport Name resolution..

[Thomas D. Charron]

  Ok, I'm a little confused here..  How are we then going to handle single users utilizing multiple transports, without forcing the users to deal with actual DNS lookups?  There HAS to be a better way of doing this..  If I'm TwOlf at jabber.org, how does jabber.org know how to reach me?  Are we forced to actually go thru the ./jabbertransport for all usage?  Here's my problem.

  Several months ago we had talked about remote server usage.  In the scheme, as I know understand it, in order for me to use, let's say the ICQ gateway, I will need my local jabber server to actually RUN the ICQ transport, unless a remote server actually has an actual DNS entry for, let's say icq.tiac.net.  While this is all (just now) starting to make sense, I'm thinking that there has to be a way to accomidate both worlds, both true domain name and aliased transports..

  The current method will work great, untill Jer wants to connect to leagion.tiac.net to the irc gateway.  Won't work, unless I actually set up a DNS alias FOR slashnet.leagion.tiac.net.  Hrm..  Perhaps that IS the best answer..  just require DNS aliasing?
---
Thomas Charron

On Mon, 12 Jul 1999 16:30:11   Jeremie wrote:
>Well, simply, foo.bar.com isn't assumed to mean the foo transport at
>bar.com.  Any hostname in an address explicitly means that address,
>there's no fudging going on there.  So #slashdot at slashnet.jabber.org would
>require a host slashnet.jabber.org with etherx running there and a
>transport that has "slashnet.jabber.org" as it's alias.  
>
>The only way to reference a transport on the internet is to have a
>hostname for it and etherx running on that host, and have the transport
>notify etherx of it's address so the data can be routed to it.
>
>Jer
>
>On Mon, 12 Jul 1999, Thomas D. Charron wrote:
>
>>   Guys, I have a quickie question about something I really haven't looked at quite yet..  How does jabber handle address <=> real world lookups?  Take these examples:
>> 
>> TwOlf at jabber.jabber.org
>> Admin at jabber.org
>> #slashdot at slashnet.jabber.org
>> 
>>     How will these address?  Here's what I'm gathering:
>> 
>> Namespace is per address, aka, Jabber.org means send it to etherx at jabber.org.  You can also append a transport at the top level, Aka: TwOlf at jabber.jabber.org would specifically route it to the transport named 'Jabber' at jabber.org.  Likewise with #slashdot at slashnet.jabber.org, except to the slashnet transport at jabber.org..  Now here's the doozie..  How does it determine this.  Here's my case:
>> 
>>     I have a domain, leagion.tiac.net.  My machine IS leagion.tiac.net, so my Jabber addy would be twolf at leagion.tiac.net.  How does jabber know NOT to route it to the leagion transport on tiac.net, but to the etherx at leagion.tiac.net.  Likewise, would twolf at jabber.leagion.tiac.net resolve corrently?
>> 
>>     I'm about to borrow some more in the source, but it occured to me as I was thinkin..
>> 
>> 
>> ---
>> Thomas Charron
>> 
>> 
>> --== Sent via Deja.com http://www.deja.com/ ==--
>> Share what you know. Learn what you don't.
>> 
>
>


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