XMPP addresses are based solely on DNS (you cannot even specify an alternate port #), and the 1.4/2.0 implementations rely on different services being able to have complete control over a domain. You really need to have one DNS entry per exposed service.
-David Waite
On Nov 24, 2003, at 9:12 AM, Glenn MacGregor wrote:
Unfortunately I am looking for a different solution. In some cases I can't
change the DNS. I am looking to change 1.4.2 and 2.0 (if necessary) to allow
for this. As far as I can tell the change could be made in two places. I
have not got any further than that so I don't yet know the ramifications of
making the changes (hope you can help with that).
I first place would be to allow the service id to contain an '@' symbol or
the second place would be in the delivery, if it is local and fails with 404
then strip everything after the '@' inclusive and try the local delivery
again.
What do you think? Will either of these work?
Thanks
----- Original Message ----- From: "Matthias Wimmer" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, November 24, 2003 10:16 AM Subject: Re: [JDEV] External component and s2s
(I guess the component is comp1.server2.domain.com ... else just delete "comp1" in the example DNS entry below.)
Yes this works. No special configuration is needed, just a corret DNS entry, e.g. the follwoing:
_xmpp-server._tcp.comp1.server2.domain.com 86400 SRV 5 0 5269 \ server2.domain.com.
Tot kijk Matthias
-- Fon: +49-(0)70 0770 07770 http://matthias.wimmer.name/ HAM: DB1MW xmpp:[EMAIL PROTECTED]
_______________________________________________ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
_______________________________________________ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
