[JDEV] UIDs

[Scott Robinson]

Interleaved response.

Scott.

* Jeremie translated into ASCII [Wed, Sep 01, 1999 at 11:56:36AM -0500][<Pine.LNX.4.10.9909011154170.2282-100000 at lor.jeremie.com>]
> Well, I have a hard time imagining why you would have 500 transports, that
> would be similiar to having 500 email servers or web servers :)
> 

AOL and other large ISPs might. Let's never exclude large servers.

> Each transport doesn't require a seperate IP address, they can all map to
> one and etherx will distribute it accordingly.  So, if you have a TON of
> transports that you don't want to manage DNS names for, you can simply add
> a "*" DNS mapping to that IP for your domain.

Why even do that? Since the "transport" name is being routed through etherx,
and since we've decided to use the MX record for routing issues (I would
suggest, though, that we do the search in reverse of the current priority
system. Jabber at the bottom, SMTP at the top.) etherx should just route to
the MX specified server and then send off the 12341234 at icq.jabber.org
message.

[snap]
> > Especially if I'm not the DNS administrator..  I'm more inclined to support
> > the 
> > [jabber://]userid[@server][/transport][/special-data] 
> > method.  Of course, since the end result is the same either way, why not
> > just make both address types legal?
> > 

Because it's easier to use DNS for routing and exclude the whole reserved
keyword transport naming system anyway.

> > BTW, The reason I put the [@server] as an optional thing is that if I'm
> > passing an ICQ address, how am I supposed to know what the server is?  So an
> > ICQ address would look like jabber://13543534/ICQ.  I guess actually the
> > notation would be more like 
> > 

Without a server the current idea would look like:

(connected to jabbertransport.jabber.org)

(sending "jabbertransport" message to jeremie)
jeremie

(sending "ICQ" message to 12341234)
12341234 at icq

(adding full domains in, like a well behaved program should)
jeremie at jabbertransport.jabber.org

(to ICQ)
12341234 at icq.jabber.org

So in the current implementation you don't need to know the server. However,
it would be handy. ex, I'm scott at aspect.net sending to jeremie at jabber.org.
What transport is jabber.org by default? jabber.org's etherx server will
have to decide.

[snap]
> > 
> > So the end result of this: jabber://userid@foo.bar.com/special-data
> > 

I'll vote for it! Jeremie in 2000!

[snap]