Re: [hybi] Multiplexing in WebSocket (Was: HyBi Design Space)

[Martin Tyler <[e-mail]>]

On Sat, Oct 17, 2009 at 3:34 AM, Ian Hickson <[e-mail]> wrote:

> You are assuming monolithic servers like Apache, with multiple frameworks
> plugged into those servers. I'm imagining 100-line perl scripts. While we
> have such differing goals, I don't think we can come to an agreement on
> this. I want the protocol to be so simple that the frameworks are
> unnecessary; that if they are used, they would be the ones implementing
> the entire protocol on the server-side. In this world, there is no server
> to handle the multiplexing across multiple frameworks.
>
>
>
Could you explain why you are 'imagining' this? It's not how things are done
now, so why do you think server side development is going to suddenly
totally change just because WebSocket is available?

Are these multiple 100 line scripts all going to be separate processes
listening on separate ports on the same server? This just doesn't sound
likely at all.


I'm imagining server side APIs that wrap this up for you, handling the
multiplexing if we go down Gregs route, but even if not you still want
something to handle the protocol for you. It would be nice if there could be
a single server side API, but that is unlikely due to the number of server
side technologies and frameworks - but something fairly consistent could be
developed.

I really don't get this 11 year olds writing perl scripts idea - have you
explained the reasons, use cases, benefits etc of this?