Closed GoogleCodeExporter closed 8 years ago
I'm definitely interested in this.
I could see Mongoose's threading being an issue--would each websocket session
consume a thread?
Original comment by jnor...@logitech.com
on 18 Apr 2012 at 6:47
Also interested on this!
Original comment by gogop...@gmail.com
on 14 Sep 2012 at 12:27
It looks like this feature is getting a lot of interest. Bumping up the
priority, and moving to https://github.com/valenok/mongoose/issues/27
Original comment by valenok
on 14 Sep 2012 at 1:20
Excellent, thanks!
Original comment by jeroen.w...@gmail.com
on 14 Sep 2012 at 1:24
Definitely appreciate it. I can help test/implement this if you need a hand.
Original comment by jnor...@logitech.com
on 14 Sep 2012 at 1:56
I've implemented a first iteration of the functionality,
https://github.com/valenok/mongoose
To see an example, checkout the code, then "cd examples && make && ./websocket"
Go to http://127.0.0.1:8080
It is crude at the moment. Client has to create, read and parse websocket
frames on it's own.
Suggestions on the API are welcome.
Original comment by valenok
on 19 Sep 2012 at 11:29
Original issue reported on code.google.com by
kbrani...@gmail.com
on 11 Nov 2011 at 5:52