I am strongly opposed to any MUST definition for any type of URL resolution.
I'm ok with inheriting / mimicking HTTP. Since it is intended to live in
the same universe as HTTP, I'm ok with it sharing mechanisms / limitations.
On Thu, Jul 21, 2011 at 1:52 PM, Iñaki Baz Castillo <ibc(_at_)aliax(_dot_)net>
wrote:
2011/7/21 Dave Cridland <dave(_at_)cridland(_dot_)net>:
It's proven impossible, despite effort, to retrofit SRV onto HTTP; there
is
no way it'll be possible to retrofit onto WS.
Right. If WS borns with no SRV (as a MUST for WS clients) then just
forget it and let inherit all the ugly limitations from HTTP protocol.
--
Iñaki Baz Castillo
<ibc(_at_)aliax(_dot_)net>
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf