Re: [hybi] Extensibility mechanisms?

[Ian Hickson <[e-mail]>]

On Mon, 19 Apr 2010, "Martin J. Dürst" wrote:
> 
> In my view, at the low end, the amateurs will use the web sockets API on the
> client side, and should use a web sockets API (e.g. a Perl package, a Ruby
> gem, or some such) on the server side. There is a very important need to make
> it easy for 'amateurs' to use web sockets, but that doesn't mean that it has
> to be easy for them to implement a web sockets API.

As is, the protocol is simple enough that you don't have to write an API 
for it on the server side -- for many simple deployments, you can just 
write the script including the Web Socket server all as one thing. I think 
that's valuable, for reasons I've explained at length today.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'