Dnia 2008-02-08, Pt o godzinie 20:54 +0000, Richard Dobson pisze: > But surely in those cases the JIDs would be something like: > > [EMAIL PROTECTED] > [EMAIL PROTECTED] > [EMAIL PROTECTED]
What I _really_ don't like with it, is mapping one namespace to many namespaces in XMPP domain. [EMAIL PROTECTED] is the same thing that @orange. and @tmobile. This is similiar case with transports, that map one legacy names to many XMPP JIDs, depending where the gateway is, causing very abstract problems... "I just switched my transport from gw.xxxx.com to gw.yyyyy.net. How do I migrate my contacts of [EMAIL PROTECTED] Oh, btw, I do want to keep the chat history so this strange thingy JRU is no good..." And with different gateways we loose the fallback to try Gateway2 when selected Gateway1 resource is not available (default highest priority resource message routing fallback). -- /\_./o__ Tomasz Sterna (/^/(_^^' http://www.xiaoka.com/ ._.(_.)_ im:[EMAIL PROTECTED]
