mashupbots/socko issues and pull requests

#119 - Socko upgrade

Pull Request - State: closed - Opened by jamiees2 about 3 years ago - 1 comment

#118 - Memory LEAK of quickstart example

Issue - State: open - Opened by ShutaoTang almost 5 years ago

#117 - Add changes from jssweb-socko repo

Pull Request - State: closed - Opened by tylernisonoff over 6 years ago

#117 - Add changes from jssweb-socko repo

Pull Request - State: closed - Opened by tylernisonoff over 6 years ago

#116 - Headers with the same name are incorrectly overwritten and are not written at all on redirect

Issue - State: open - Opened by ccankov over 6 years ago

#116 - Headers with the same name are incorrectly overwritten and are not written at all on redirect

Issue - State: open - Opened by ccankov over 6 years ago

#115 - Add WebSocket Compression

Pull Request - State: open - Opened by alexcole almost 8 years ago - 1 comment

#114 - Removes space in link to fix it on web site

Pull Request - State: closed - Opened by colindean almost 8 years ago - 1 comment

#113 - wish this was still in active development :/

Issue - State: open - Opened by bthibault almost 9 years ago - 8 comments

#113 - wish this was still in active development :/

Issue - State: open - Opened by bthibault almost 9 years ago - 8 comments

#113 - wish this was still in active development :/

Issue - State: open - Opened by bthibault almost 9 years ago - 8 comments

#112 - Add information about the need to release netty's buffers after message processing in WebSocket

Issue - State: open - Opened by yeputons about 9 years ago - 4 comments

#112 - Add information about the need to release netty's buffers after message processing in WebSocket

Issue - State: open - Opened by yeputons about 9 years ago - 4 comments

#112 - Add information about the need to release netty's buffers after message processing in WebSocket

Issue - State: open - Opened by yeputons about 9 years ago - 4 comments

#111 - Memory Leak: After calling toBytes on DefaultHttpContent, when the content is garbage collected .release() is never called on the buffer.

Issue - State: open - Opened by malibuworkcrew over 9 years ago

#111 - Memory Leak: After calling toBytes on DefaultHttpContent, when the content is garbage collected .release() is never called on the buffer.

Issue - State: open - Opened by malibuworkcrew over 9 years ago

#111 - Memory Leak: After calling toBytes on DefaultHttpContent, when the content is garbage collected .release() is never called on the buffer.

Issue - State: open - Opened by malibuworkcrew over 9 years ago

#111 - Memory Leak: After calling toBytes on DefaultHttpContent, when the content is garbage collected .release() is never called on the buffer.

Issue - State: open - Opened by malibuworkcrew over 9 years ago

#110 - Feature UUID serialization

Pull Request - State: closed - Opened by mubarak over 9 years ago

#110 - Feature UUID serialization

Pull Request - State: closed - Opened by mubarak over 9 years ago

#110 - Feature UUID serialization

Pull Request - State: closed - Opened by mubarak over 9 years ago

#110 - Feature UUID serialization

Pull Request - State: closed - Opened by mubarak over 9 years ago

#110 - Feature UUID serialization

Pull Request - State: closed - Opened by mubarak over 9 years ago

#109 - Adding json4s-ext

Pull Request - State: closed - Opened by mubarak over 9 years ago

#109 - Adding json4s-ext

Pull Request - State: closed - Opened by mubarak over 9 years ago

#109 - Adding json4s-ext

Pull Request - State: closed - Opened by mubarak over 9 years ago

#109 - Adding json4s-ext

Pull Request - State: closed - Opened by mubarak over 9 years ago