[JDEV] Unique IDs

Scott Robinson scott at tranzoa.com
Wed Aug 11 09:51:01 CDT 1999

Interleaved response.


* Anders Qvist translated into ASCII [Wed, Aug 11, 1999 at 02:17:34PM +0200][<Pine.LNX.3.96.990811140337.12899F-100000 at valdez.netg.se>]
> I think Jabber should include a mechanism for uniquely IDing each message
> that gets sent. Every time the server receives a message, it should tag it

me too!

> IDs should be constructed using server time, sender username, a sequence
> number and server FQDN. Kind of like some mail servers do with email.

Now is a good time to bring up routing, if we're going to start talking
about core functionality. A couple of issues with our current "routing" spec
were brought up in the channel by a lurker on our list.

a) How are we handling vhosts?
b) How are we multiple hosts?
c) What about systems that cannot be contacted directly? Can we setup a
Jabber Server->Jabber Server routing system?
d) Will we support a Jabber DNS extension. The particular lurker happened to
be an admin over at disneyonline and said that "MX" records were a god-send
for him. Can we create the same thing for Jabber? ("IX" was suggested.) This
could handle domain issues on both support and centralization.

> This should probably be Jabbertransport core functionality.

me too!

> Anders "Quest" Qvist
> NetGuide Scandinavia
> -- Why suffer scarcity? Look for the Open Source and enter a world of plenty!
> _______________________________________________
> jdev mailing list
> jdev at jabber.org
> http://mailman.jabber.org/listinfo/jdev

More information about the JDev mailing list