Ecosyste.ms: Issues

An open API service for providing issue and pull request metadata for open source projects.

GitHub / mashupbots/socko issues and pull requests

#91 - No resource for my/package in RestRegistry

Issue - State: closed - Opened by chenweiyj almost 11 years ago - 14 comments

#90 - two new questions on stackoverflow

Issue - State: closed - Opened by simbo1905 almost 11 years ago

#90 - two new questions on stackoverflow

Issue - State: closed - Opened by simbo1905 almost 11 years ago

#90 - two new questions on stackoverflow

Issue - State: closed - Opened by simbo1905 almost 11 years ago

#90 - two new questions on stackoverflow

Issue - State: closed - Opened by simbo1905 almost 11 years ago

#90 - two new questions on stackoverflow

Issue - State: closed - Opened by simbo1905 almost 11 years ago

#89 - Guide error?

Issue - State: closed - Opened by cube-drone almost 11 years ago - 2 comments

#89 - Guide error?

Issue - State: closed - Opened by cube-drone almost 11 years ago - 2 comments

#89 - Guide error?

Issue - State: closed - Opened by cube-drone almost 11 years ago - 2 comments

#89 - Guide error?

Issue - State: closed - Opened by cube-drone almost 11 years ago - 2 comments

#89 - Guide error?

Issue - State: closed - Opened by cube-drone almost 11 years ago - 2 comments

#88 - Upgrade to scala 2.11

Issue - State: closed - Opened by ForNeVeR almost 11 years ago - 5 comments

#88 - Upgrade to scala 2.11

Issue - State: closed - Opened by ForNeVeR almost 11 years ago - 5 comments

#88 - Upgrade to scala 2.11

Issue - State: closed - Opened by ForNeVeR almost 11 years ago - 5 comments

#88 - Upgrade to scala 2.11

Issue - State: closed - Opened by ForNeVeR almost 11 years ago - 5 comments

#87 - Akka 2.3.0 compatibility

Issue - State: closed - Opened by atemerev almost 11 years ago - 2 comments

#87 - Akka 2.3.0 compatibility

Issue - State: closed - Opened by atemerev almost 11 years ago - 2 comments

#87 - Akka 2.3.0 compatibility

Issue - State: closed - Opened by atemerev almost 11 years ago - 2 comments

#87 - Akka 2.3.0 compatibility

Issue - State: closed - Opened by atemerev almost 11 years ago - 2 comments

#86 - wss

Issue - State: closed - Opened by ghost almost 11 years ago - 1 comment

#86 - wss

Issue - State: closed - Opened by ghost almost 11 years ago - 1 comment

#86 - wss

Issue - State: closed - Opened by ghost almost 11 years ago - 1 comment

#85 - Autobahn test suite report

Issue - State: closed - Opened by ghost almost 11 years ago - 2 comments

#85 - Autobahn test suite report

Issue - State: closed - Opened by ghost almost 11 years ago - 2 comments

#85 - Autobahn test suite report

Issue - State: closed - Opened by ghost almost 11 years ago - 2 comments

#84 - Use custom handlers

Pull Request - State: closed - Opened by thirstycrow almost 11 years ago

#84 - Use custom handlers

Pull Request - State: closed - Opened by thirstycrow almost 11 years ago

#84 - Use custom handlers

Pull Request - State: closed - Opened by thirstycrow almost 11 years ago

#83 - add response write method with status and headers parameters

Pull Request - State: closed - Opened by rossajmcd about 11 years ago - 1 comment

#83 - add response write method with status and headers parameters

Pull Request - State: closed - Opened by rossajmcd about 11 years ago - 1 comment

#83 - add response write method with status and headers parameters

Pull Request - State: closed - Opened by rossajmcd about 11 years ago - 1 comment

#83 - add response write method with status and headers parameters

Pull Request - State: closed - Opened by rossajmcd about 11 years ago - 1 comment

#83 - add response write method with status and headers parameters

Pull Request - State: closed - Opened by rossajmcd about 11 years ago - 1 comment

#82 - Support for Websocket fallbacks

Issue - State: closed - Opened by chiappone about 11 years ago - 4 comments

#82 - Support for Websocket fallbacks

Issue - State: closed - Opened by chiappone about 11 years ago - 4 comments

#82 - Support for Websocket fallbacks

Issue - State: closed - Opened by chiappone about 11 years ago - 4 comments

#82 - Support for Websocket fallbacks

Issue - State: closed - Opened by chiappone about 11 years ago - 4 comments

#82 - Support for Websocket fallbacks

Issue - State: closed - Opened by chiappone about 11 years ago - 4 comments

#81 - event.readBinary() causes UnsupportedOperationException

Issue - State: closed - Opened by chiappone about 11 years ago - 1 comment

#81 - event.readBinary() causes UnsupportedOperationException

Issue - State: closed - Opened by chiappone about 11 years ago - 1 comment

#80 - some question for socko Routers

Issue - State: closed - Opened by marsxu1984 about 11 years ago - 3 comments

#80 - some question for socko Routers

Issue - State: closed - Opened by marsxu1984 about 11 years ago - 3 comments

#80 - some question for socko Routers

Issue - State: closed - Opened by marsxu1984 about 11 years ago - 3 comments

#80 - some question for socko Routers

Issue - State: closed - Opened by marsxu1984 about 11 years ago - 3 comments

#79 - Remove setting of SPDY headers

Issue - State: closed - Opened by veebs about 11 years ago

#79 - Remove setting of SPDY headers

Issue - State: closed - Opened by veebs about 11 years ago

#79 - Remove setting of SPDY headers

Issue - State: closed - Opened by veebs about 11 years ago

#78 - ReflectUtil: do not count in classes with special char when load from JAR

Pull Request - State: closed - Opened by gnawux about 11 years ago - 1 comment

#78 - ReflectUtil: do not count in classes with special char when load from JAR

Pull Request - State: closed - Opened by gnawux about 11 years ago - 1 comment

#78 - ReflectUtil: do not count in classes with special char when load from JAR

Pull Request - State: closed - Opened by gnawux about 11 years ago - 1 comment

#78 - ReflectUtil: do not count in classes with special char when load from JAR

Pull Request - State: closed - Opened by gnawux about 11 years ago - 1 comment

#78 - ReflectUtil: do not count in classes with special char when load from JAR

Pull Request - State: closed - Opened by gnawux about 11 years ago - 1 comment

#77 - SPDY not working with v0.4.0

Issue - State: closed - Opened by veebs about 11 years ago - 1 comment

#76 - Need a safe way to resolve the webserver.webSocketConnections when defining Routes

Issue - State: closed - Opened by simbo1905 about 11 years ago - 2 comments

#76 - Need a safe way to resolve the webserver.webSocketConnections when defining Routes

Issue - State: closed - Opened by simbo1905 about 11 years ago - 2 comments

#76 - Need a safe way to resolve the webserver.webSocketConnections when defining Routes

Issue - State: closed - Opened by simbo1905 about 11 years ago - 2 comments

#76 - Need a safe way to resolve the webserver.webSocketConnections when defining Routes

Issue - State: closed - Opened by simbo1905 about 11 years ago - 2 comments

#76 - Need a safe way to resolve the webserver.webSocketConnections when defining Routes

Issue - State: closed - Opened by simbo1905 about 11 years ago - 2 comments

#75 - api change design question: passing webServer.webSocketConnections to actors

Issue - State: closed - Opened by simbo1905 about 11 years ago - 9 comments

#75 - api change design question: passing webServer.webSocketConnections to actors

Issue - State: closed - Opened by simbo1905 about 11 years ago - 9 comments

#75 - api change design question: passing webServer.webSocketConnections to actors

Issue - State: closed - Opened by simbo1905 about 11 years ago - 9 comments

#75 - api change design question: passing webServer.webSocketConnections to actors

Issue - State: closed - Opened by simbo1905 about 11 years ago - 9 comments

#75 - api change design question: passing webServer.webSocketConnections to actors

Issue - State: closed - Opened by simbo1905 about 11 years ago - 9 comments

#74 - SPDY not performing as expected with the StaticContentHandler

Issue - State: closed - Opened by Bongani about 11 years ago - 9 comments

#74 - SPDY not performing as expected with the StaticContentHandler

Issue - State: closed - Opened by Bongani about 11 years ago - 9 comments

#74 - SPDY not performing as expected with the StaticContentHandler

Issue - State: closed - Opened by Bongani about 11 years ago - 9 comments

#74 - SPDY not performing as expected with the StaticContentHandler

Issue - State: closed - Opened by Bongani about 11 years ago - 9 comments

#73 - Does Socko support Basic Authentication

Issue - State: closed - Opened by chiappone over 11 years ago - 1 comment

#73 - Does Socko support Basic Authentication

Issue - State: closed - Opened by chiappone over 11 years ago - 1 comment

#73 - Does Socko support Basic Authentication

Issue - State: closed - Opened by chiappone over 11 years ago - 1 comment

#72 - ReflectUtil don't check some scala class will contain "$" in classname

Issue - State: closed - Opened by marsxu1984 over 11 years ago - 2 comments

#72 - ReflectUtil don't check some scala class will contain "$" in classname

Issue - State: closed - Opened by marsxu1984 over 11 years ago - 2 comments

#72 - ReflectUtil don't check some scala class will contain "$" in classname

Issue - State: closed - Opened by marsxu1984 over 11 years ago - 2 comments

#71 - I can't handler CloseWebSocketFrame event

Issue - State: closed - Opened by marsxu1984 over 11 years ago - 7 comments

#71 - I can't handler CloseWebSocketFrame event

Issue - State: closed - Opened by marsxu1984 over 11 years ago - 7 comments

#71 - I can't handler CloseWebSocketFrame event

Issue - State: closed - Opened by marsxu1984 over 11 years ago - 7 comments

#71 - I can't handler CloseWebSocketFrame event

Issue - State: closed - Opened by marsxu1984 over 11 years ago - 7 comments

#71 - I can't handler CloseWebSocketFrame event

Issue - State: closed - Opened by marsxu1984 over 11 years ago - 7 comments

#69 - No way to issue two headers with the same name

Issue - State: closed - Opened by konstantin-azarov over 11 years ago - 6 comments

#69 - No way to issue two headers with the same name

Issue - State: closed - Opened by konstantin-azarov over 11 years ago - 6 comments

#69 - No way to issue two headers with the same name

Issue - State: closed - Opened by konstantin-azarov over 11 years ago - 6 comments

#68 - Non deterministic reflection errors on start up

Issue - State: closed - Opened by techdubb over 11 years ago - 3 comments

#68 - Non deterministic reflection errors on start up

Issue - State: closed - Opened by techdubb over 11 years ago - 3 comments

#68 - Non deterministic reflection errors on start up

Issue - State: closed - Opened by techdubb over 11 years ago - 3 comments

#68 - Non deterministic reflection errors on start up

Issue - State: closed - Opened by techdubb over 11 years ago - 3 comments

#67 - Detecting if a websocket has been disconnected

Issue - State: closed - Opened by Bongani over 11 years ago - 4 comments

#67 - Detecting if a websocket has been disconnected

Issue - State: closed - Opened by Bongani over 11 years ago - 4 comments

#67 - Detecting if a websocket has been disconnected

Issue - State: closed - Opened by Bongani over 11 years ago - 4 comments

#67 - Detecting if a websocket has been disconnected

Issue - State: closed - Opened by Bongani over 11 years ago - 4 comments

#67 - Detecting if a websocket has been disconnected

Issue - State: closed - Opened by Bongani over 11 years ago - 4 comments

#66 - Fix FileUpload and WebSocket Chat Problems

Pull Request - State: closed - Opened by thirstycrow over 11 years ago - 11 comments

#66 - Fix FileUpload and WebSocket Chat Problems

Pull Request - State: closed - Opened by thirstycrow over 11 years ago - 11 comments

#66 - Fix FileUpload and WebSocket Chat Problems

Pull Request - State: closed - Opened by thirstycrow over 11 years ago - 11 comments

#66 - Fix FileUpload and WebSocket Chat Problems

Pull Request - State: closed - Opened by thirstycrow over 11 years ago - 11 comments

#65 - FileUpload and WebSocket Chat not working after Netty 4 Upgrade

Issue - State: closed - Opened by veebs over 11 years ago - 1 comment

#64 - Firefox does not connect to web socket

Issue - State: closed - Opened by veebs over 11 years ago