On Wed Oct  7 22:38:05 2009, Joe Hildebrand wrote:
What about XEP-156? For web-only clients that don't have DNS access, they can usually have the polling URL configured in, and for desktop clients, they can look up a TXT record to figure out where to poll.

Why do we have to hard-code a path?

I think the intention here is that web-only clients need the URL hard-coded in, and the argument is that because this is often less than intuitive, it'd be useful if the vast majority of BOSH implementations listened to, and expected, the same path.

The thing is, my understanding is that for typical "real" deployments, the path is reverse proxied by a "real" webserver anyway, so I wonder how much work we're saving here.

Finally, I'd just like to say U-NAPTR. Just to see the looks of horror.

Dave.
--
Dave Cridland - mailto:[email protected] - xmpp:[email protected]
 - acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/
 - http://dave.cridland.net/
Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade

Reply via email to