Is there a standard for locating an XMPP server, just like there is for
locating an incoming email server? If not, are there any benefits in
defining one specifically for Wave? Disadvantages? Would this go against the
XMPP spec?
Fahad Sadah


2009/10/28 Peter Saint-Andre <[email protected]>

>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 10/27/09 7:00 PM, Daniel Danopia wrote:
> > I an running a web server at danopia.net and I run my wave server at
> > wave.danopia.net, which CNAMEs to home.danopia.net, which CNAMEs to
> > danopia.no-ip.org. I don't think it's necesary to use wave. but it's
> > recommended. You probably can use whatever, but XMPP requires each
> > component to have a subdomain, and Wave uses wave. for this.
>
> In fact this is not required by XMPP, but it is a common practice among
> XMPP server projects (going back to the original jabberd server in 1999).
>
> > My custom
> > provider works with *any* JID, as long as it is labeled "google-wave".
> > I personally run my custom provider at newwave.danopia.net. and the
> > only sideaffect is some servers ignoring me completely because I don't
> > have _xmpp-server._tcp.newwave.danopia.net.
>
> DNS SRV records are not absolutely mandatory to run XMPP-based services,
> unless you are running them on non-standard ports.
>
> Peter
>
> - --
> Peter Saint-Andre
> https://stpeter.im/
>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.8 (Darwin)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAkrnngEACgkQNL8k5A2w/vxofgCdF96AgqKzO9OAAjIL0BDnbw+j
> VSEAmwZkMy4boAX0SiGa/4YPbRuafpkJ
> =Yz4Y
> -----END PGP SIGNATURE-----
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Wave 
Protocol" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/wave-protocol?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to