Re: [Erlyaws-list] argh, chrome 14 broke yaws winsockets :(

On Sat, Oct 1, 2011 at 2:55 AM, Jan Bothma <jbothma@...> wrote:
>
> Regarding maintaining support... According to
> http://blog.chromium.org/search/label/websockets, "The WebSocket
> protocol specification is now largely stable, having solved previous
> security concerns." which suggests that other vendors are likely to
> add support for the new protocol (hybi 10) and enable it by default,
> while the old protocol (hixie 76) is what prompted some to disable it
> by default.
>
> If the security concerns are dealt with, I think there's little
> argument for keeping the old protocols and a lot of argument for
> supporting the new.
I believe most folks here using WebSockets today understand it's a
moving target, and expect to have to modify their code to keep up with
evolution of the specification. The primary issue isn't so much Yaws,
as we can fix that, but rather browser support, but of course people
can just use whatever Yaws version supports the flavor of WebSockets
they need most. So, my own preference is not to try to support old and
new versions of WebSockets at the same time, but rather would like to
just upgrade Yaws to the latest spec and drop support for old
WebSockets versions. I can't speak for Klacke, but if he has a
preference here, don't worry, he'll let us know.
And yes, all patches and help to bring things up to date are appreciated.
--steve

Community

Help

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

I agree to receive quotes, newsletters and other information from sourceforge.net and its partners regarding IT services and products. I understand that I can withdraw my consent at any time. Please refer to our Privacy Policy or Contact Us for more details