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 <i...@aliax.net> wrote: > 2011/7/21 Dave Cridland <d...@cridland.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 > <i...@aliax.net> >
_______________________________________________ Ietf mailing list Ietf@ietf.org https://www.ietf.org/mailman/listinfo/ietf
