what about a new result type {websocket,Pid::pid(),Active::bool()} ?
where :
- Pid is the websocket owner pid
- Active to set the socket to active mode or not
Add in yaws_api :
-> websocket_send
-> websocket_recv
we could reuse some code from davide for framing management.
what do you think about it ?
Thank you for your help

Hi all,

Just uploaded a Web Sockets ewgi implementation that is working on Yaws, Mochiweb and Inets.
To use it just grab the last code from:
http://github.com/davide/ewgi and http://github.com/davide/ewgi_examples.
Start the server via cd ewgi_examples; ./start.sh default
And point Chromium to http://localhost/websocket.

An usage example can be found in:
Haven't quite figured out how to get "wss://" to work though...

The code was inspired by the other implementations that popped in erlang-questions this week, so I'd like to thank the various authors. :)

Davide :)

On Thu, Dec 17, 2009 at 9:36 PM, Claes Wikstrom <klacke@tail-f.com> wrote:
wde wrote:
> Hello all,
> Does someone actually use yaws and the websocket feature introduced with HTML5 ?

Not to my knowledge, thus excellent opportunity to be the first !! and publish.


This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
Erlyaws-list mailing list