[ANN] Swazoo has now WebSocket support

> Dear Smalltalkers,
>
> Past few days I worked on WebSocket implementation in Swazoo Smalltalk
> web server [1], in coordination with Philippe Marschall from Seaside [4]
> and Nicolas Petton from Iliad [5] devteams, so together with me from
> Aida/Web [3] our cooperation ensures that this implementation is ready
> to be adapted for all three main web frameworks.
>
> Why WebSocket? Because it will replace current Comet hacks to enable a
> bidirectional messaging between browser and web application, specially
> for web app to send something back to the browser without waiting for
> user to click something. Read a bit more about WebSocket here:
>
> http://dev.opera.com/articles/view/introducing-web-sockets/
>
> WebSocket as browser supported technology enables opening an always
> present channel, so that web app can send commands like update some
> element of the webpage at any time. That's why WebSocket is ideal for so
> called "real-time" web.
>
> You are invited to look at the code for Squeak/Pharo as Swazoo2.3beta1.1
> at http://www.squeaksource.org/Swazoo.html
>
> A bit more about WebSocket in Swazoo:
>
> http://www.swazoo.org/websocket
>
> Best regards
> Janko
> Swazoo maintainer
>
> [1] Swazoo WebSocket support
>    http://www.swazoo.org/websocket
> [2] Introducing WebSockets
>    http://dev.opera.com/articles/view/introducing-web-sockets/
> [3] Aida/Web
>    http://www.aidaweb.si
> [4] Seaside
>    http://www.seaside.st
> [5] Iliad
>    http://www.iliadproject.org
>
> _______________________________________________
> seaside mailing list
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
>

> Dear Smalltalkers,
>
> Past few days I worked on WebSocket implementation in Swazoo Smalltalk
> web server [1], in coordination with Philippe Marschall from Seaside [4]
> and Nicolas Petton from Iliad [5] devteams, so together with me from
> Aida/Web [3] our cooperation ensures that this implementation is ready
> to be adapted for all three main web frameworks.
>
> Why WebSocket? Because it will replace current Comet hacks to enable a
> bidirectional messaging between browser and web application, specially
> for web app to send something back to the browser without waiting for
> user to click something. Read a bit more about WebSocket here:
>
>        http://dev.opera.com/articles/view/introducing-web-sockets/
>
> WebSocket as browser supported technology enables opening an always
> present channel, so that web app can send commands like update some
> element of the webpage at any time. That's why WebSocket is ideal for so
> called "real-time" web.
>
> You are invited to look at the code for Squeak/Pharo as Swazoo2.3beta1.1
> at http://www.squeaksource.org/Swazoo.html
>
> A bit more about WebSocket in Swazoo:
>
>        http://www.swazoo.org/websocket

> On 12/9/2010 4:40 AM, Philippe Marschall wrote:
>> Looks like we have to wait for a new version of the protocol:
>>
>>  http://hacks.mozilla.org/2010/12/websockets-disabled-in-firefox-4/
>>
>
> This is *seriously* bad news. CONNECT through port 80 (as required by the connect based handshake) is disabled in virtually all proxy installations, meaning that adoption of the connect based handshake will be extremely slow and painful for real world applications :-(((
>
> Cheers,
>  - Andreas
> _______________________________________________
> seaside mailing list
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside