[JDEV] UIDs

[Jim Phillips]

The only issue I have with this is as follows..  If I'm understanding this
properly, you're requiring that each transport has its own DNS name and IP
address.  Or will etherx be able to pass to the right transport just on
name?  That part is confusing me..  But the real issue I take with this is,
what happens if I have 500 transports?  Does this mean that I have to add
500 entries to my DNS server?? What a painful task that might be..
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?

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 

jabber://<address>[/<transport>][/<special-data>]

Jim

-----Original Message-----
From: Jeremie [mailto:jeremie at jabber.org]
Sent: Wednesday, September 01, 1999 11:32 AM
To: jdev at jabber.org
Subject: Re: [JDEV] UIDs


[snip]

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

==> The [jabber://] is not used internally in Jabber, only in web/URI
settings where appropriate.

==> The [userid] my be dropped for special public server-only queries.

==> The [foo.bar.com] is the address of any server/transport entity in
Jabber.

==> The [/special-data] is passed to the transport to handle as it wishes
for special purposes or internal routing data.

Lovin it, if everyone is ok with this it works for me!  The only
code/architecture changes required are to pass around that [/special-data]
which I can add into etherx without too much difficulty for 0.7.

Great, thanks!

Jer


_______________________________________________
jdev mailing list
jdev at jabber.org
http://mailman.jabber.org/listinfo/jdev