The only way I could see client support working is if the machine(s) that
the A record pointed to also did redirection to an appropriate host, i.e.
1. client uses SRV if supported
2. if SRV is not supported, connect to last known IP for that host
3. if IP is not cached or connection fails, connect to the machine pointed
to by the A record
4. the A record machine just runs a fake c2s component which redirects you
to an appropriate machine, i.e.
C: foo
S: im.jabber.org
-server disconnects-
-client connects to im.jabber.org-
C:
To: "Jeremie" <[EMAIL PROTECTED]>
Sent: Monday, January 14, 2002 3:28 PM
Subject: Re[4]: [JDEV] SRV record and sending S2S
> Hi,
>
> Thanks for the reply Jeremie, I'll be trying it again if the guy who
> hosts my domain has time to add the SRV record again (we had problems
> with automatic tools so it got removed) :)
>
> >_jabber._tcpIN SRV 30 30 5269 servera.domain.org.
>
> Does any one have any thoughts on a how a client should use SRV
> records? If the port given in the SRV record is the S2S port then how
> would the client determine which port to connect to?
>
> Thomas Parslow (PatRat) ICQ #:26359483
> Rat Software
> http://www.rat-software.com/
> Please leave quoted text in place when replying
>
> ___
> jdev mailing list
> [EMAIL PROTECTED]
> http://mailman.jabber.org/listinfo/jdev
>
___
jdev mailing list
[EMAIL PROTECTED]
http://mailman.jabber.org/listinfo/jdev
