Websockets support #26

Closed
RJ opened this Issue Dec 8, 2010 · 5 comments

4 participants

@RJ
RJ commented Dec 8, 2010

I've squashed my websockets patch into my mochiweb fork here: https://github.com/RJ/mochiweb/

Relevant commit: RJ@0e94193

Contains an example showing websockets over ssl with origin validation, and some tests for header parsing and decoding websockets frames.

I will endeavour to keep this working, as and when the websockets spec changes.

@lemenkov
Mochi Media, Inc. member

Sorry for the hiatus, Richard. I plan to review it (and merge if no issues will be found) very soon.

@RJ
RJ commented Mar 21, 2011

I'm seeing an issue with lingering processes after clients disconnect, that I haven't fully diagnosed yet.

Can't reproduce in test environment yet, but I'm suspicious that there's a bug in the websocket code somewhere. Will update this ticket once I know more. Would be great to get a review none-the-less, will hopefully give me a clue where to look.

@hyperthunk

Is this work still ongoing? I see a tag 'active-passive' with the websockets support enabled, but other than that it appears to be stalled. Is there anything the rest of us can do to help move it along?

@RJ
RJ commented Apr 2, 2012

I'm not working on this any more.

I'm currently using misultin in production, using its websocket support which I contributed to.
See the websocket related code from here: https://github.com/ostinelli/misultin/blob/master/src/

Transplanting the guts of misultin websocket code into mochiweb shouldn't be too tricky - happy to answer questions about that if anyone feels the urge :)

RJ

@k3nn7 k3nn7 referenced this issue Dec 25, 2013
Merged

Websocket support #120

@etrepum
Mochi Media, Inc. member

Closed in favor of #120

@etrepum etrepum closed this Dec 25, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment