WebSocket.Upgrade

[Josh Perry]

I was watching Miguel's state of the union presentation, and when he
demoed Manos he used what looks like a static function
WebSocket.Upgrade. Does this functionality exist in Manos? I can't
seem to find it anywhere.

Josh

[Jackson Harper]

Hey!

You can find it here:

https://github.com/jacksonh/ManosSmoothie/blob/master/WebSocket.cs

Jackson

[Josh Perry]

Thanks Jackson!

Is there a reason this isn't in the Manos codebase? Just curious if
it
perhaps has been obsoleted or if it was just an experiment and
perhaps
needs some stabilization work done.

Josh

[Jackson Harper]

Yeah it's many just experimental right now and needs to be fleshed out a little more.

Jackson

[Stuart Johnson]

What does this do? Does it add websocket support to Manos?

I have not got into websockets yet, so i dont know if this is possible,
but I looking for a web server that can dish out web pages, and also act
as a websocket server on the same port (80/443).

[Jackson Harper]

It does. Although its somewhat experimental (along with web sockets).

Depending on your needs, the easiest thing to do is to usually setup a
subdomain for web sockets. So something like:

www.manos.com running django
and
streams.manos.com running node.js

Jackson

[Stuart Johnson]

I see, thanks.

[Stuart Johnson]

I was just reading on Stackoverflow, that WebSockets have a HTTP-compatible handshake so that HTTP servers can share their default HTTP and HTTPS ports (80 and 443) with a Web Sockets server.

I was thinking about embedding Manos into an existing server application I have, so it can perform both tasks on the same ports.