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
#64 - Firefox does not connect to web socket
Issue -
State: closed - Opened by veebs about 11 years ago
#63 - Netty4
Pull Request -
State: closed - Opened by thirstycrow about 11 years ago
- 4 comments
#63 - Netty4
Pull Request -
State: closed - Opened by thirstycrow about 11 years ago
- 4 comments
#63 - Netty4
Pull Request -
State: closed - Opened by thirstycrow about 11 years ago
- 4 comments
#63 - Netty4
Pull Request -
State: closed - Opened by thirstycrow about 11 years ago
- 4 comments
#62 - websocket session tracking
Issue -
State: closed - Opened by simbo1905 about 11 years ago
- 1 comment
#62 - websocket session tracking
Issue -
State: closed - Opened by simbo1905 about 11 years ago
- 1 comment
#62 - websocket session tracking
Issue -
State: closed - Opened by simbo1905 about 11 years ago
- 1 comment
#62 - websocket session tracking
Issue -
State: closed - Opened by simbo1905 about 11 years ago
- 1 comment
#62 - websocket session tracking
Issue -
State: closed - Opened by simbo1905 about 11 years ago
- 1 comment
#61 - Update Depdendancies
Issue -
State: closed - Opened by veebs about 11 years ago
#61 - Update Depdendancies
Issue -
State: closed - Opened by veebs about 11 years ago
#60 - Use ActorRefFactory instead of ActorSystem in WebService
Pull Request -
State: closed - Opened by skylve about 11 years ago
- 4 comments
#60 - Use ActorRefFactory instead of ActorSystem in WebService
Pull Request -
State: closed - Opened by skylve about 11 years ago
- 4 comments
#60 - Use ActorRefFactory instead of ActorSystem in WebService
Pull Request -
State: closed - Opened by skylve about 11 years ago
- 4 comments
#60 - Use ActorRefFactory instead of ActorSystem in WebService
Pull Request -
State: closed - Opened by skylve about 11 years ago
- 4 comments
#60 - Use ActorRefFactory instead of ActorSystem in WebService
Pull Request -
State: closed - Opened by skylve about 11 years ago
- 4 comments
#59 - Benchmarking socko
Issue -
State: closed - Opened by Bongani about 11 years ago
- 9 comments
#59 - Benchmarking socko
Issue -
State: closed - Opened by Bongani about 11 years ago
- 9 comments
#59 - Benchmarking socko
Issue -
State: closed - Opened by Bongani about 11 years ago
- 9 comments
#59 - Benchmarking socko
Issue -
State: closed - Opened by Bongani about 11 years ago
- 9 comments
#58 - not sure where to discuss the approach socko takes to websockets
Issue -
State: closed - Opened by simbo1905 about 11 years ago
- 3 comments
#58 - not sure where to discuss the approach socko takes to websockets
Issue -
State: closed - Opened by simbo1905 about 11 years ago
- 3 comments
#57 - Path Segments
Issue -
State: closed - Opened by Bongani about 11 years ago
- 2 comments
#57 - Path Segments
Issue -
State: closed - Opened by Bongani about 11 years ago
- 2 comments
#56 - Incompatibility with Google guava
Issue -
State: closed - Opened by ychaze about 11 years ago
- 2 comments
#56 - Incompatibility with Google guava
Issue -
State: closed - Opened by ychaze about 11 years ago
- 2 comments
#56 - Incompatibility with Google guava
Issue -
State: closed - Opened by ychaze about 11 years ago
- 2 comments
#56 - Incompatibility with Google guava
Issue -
State: closed - Opened by ychaze about 11 years ago
- 2 comments
#55 - UberJar bundling of SockoWeb and passing external configuation and logback handling
Issue -
State: closed - Opened by conikeec about 11 years ago
- 4 comments
#55 - UberJar bundling of SockoWeb and passing external configuation and logback handling
Issue -
State: closed - Opened by conikeec about 11 years ago
- 4 comments
#55 - UberJar bundling of SockoWeb and passing external configuation and logback handling
Issue -
State: closed - Opened by conikeec about 11 years ago
- 4 comments
#54 - WebSockets: WebSocketFrameEvent.writeBinary() missing type parameter
Issue -
State: closed - Opened by pvorb about 11 years ago
- 2 comments
#54 - WebSockets: WebSocketFrameEvent.writeBinary() missing type parameter
Issue -
State: closed - Opened by pvorb about 11 years ago
- 2 comments
#53 - Feature Request: Easy Testing Hooks
Issue -
State: closed - Opened by pr1001 over 11 years ago
- 2 comments
#53 - Feature Request: Easy Testing Hooks
Issue -
State: closed - Opened by pr1001 over 11 years ago
- 2 comments
#52 - Creating a unique key map from a WebSocketFrameEvent
Issue -
State: closed - Opened by Bongani over 11 years ago
- 11 comments
#52 - Creating a unique key map from a WebSocketFrameEvent
Issue -
State: closed - Opened by Bongani over 11 years ago
- 11 comments
#52 - Creating a unique key map from a WebSocketFrameEvent
Issue -
State: closed - Opened by Bongani over 11 years ago
- 11 comments
#52 - Creating a unique key map from a WebSocketFrameEvent
Issue -
State: closed - Opened by Bongani over 11 years ago
- 11 comments
#52 - Creating a unique key map from a WebSocketFrameEvent
Issue -
State: closed - Opened by Bongani over 11 years ago
- 11 comments
#51 - Initiate HTTP/S and SPDY connections from Socko
Issue -
State: open - Opened by veebs over 11 years ago
- 1 comment
#51 - Initiate HTTP/S and SPDY connections from Socko
Issue -
State: open - Opened by veebs over 11 years ago
- 1 comment
#50 - Timeout keep-alive connections
Issue -
State: closed - Opened by veebs over 11 years ago
- 1 comment
#50 - Timeout keep-alive connections
Issue -
State: closed - Opened by veebs over 11 years ago
- 1 comment
#50 - Timeout keep-alive connections
Issue -
State: closed - Opened by veebs over 11 years ago
- 1 comment
#50 - Timeout keep-alive connections
Issue -
State: closed - Opened by veebs over 11 years ago
- 1 comment
#50 - Timeout keep-alive connections
Issue -
State: closed - Opened by veebs over 11 years ago
- 1 comment
#49 - Websocket timeout
Issue -
State: closed - Opened by JoshZA over 11 years ago
- 9 comments
#49 - Websocket timeout
Issue -
State: closed - Opened by JoshZA over 11 years ago
- 9 comments
#49 - Websocket timeout
Issue -
State: closed - Opened by JoshZA over 11 years ago
- 9 comments
#49 - Websocket timeout
Issue -
State: closed - Opened by JoshZA over 11 years ago
- 9 comments
#49 - Websocket timeout
Issue -
State: closed - Opened by JoshZA over 11 years ago
- 9 comments
#48 - NullPointerException within RequestHandler
Issue -
State: closed - Opened by analytically over 11 years ago
- 7 comments
#48 - NullPointerException within RequestHandler
Issue -
State: closed - Opened by analytically over 11 years ago
- 7 comments
#48 - NullPointerException within RequestHandler
Issue -
State: closed - Opened by analytically over 11 years ago
- 7 comments
#48 - NullPointerException within RequestHandler
Issue -
State: closed - Opened by analytically over 11 years ago
- 7 comments
#47 - Authentication of WebSockets with Session
Issue -
State: closed - Opened by trevex over 11 years ago
- 2 comments
#47 - Authentication of WebSockets with Session
Issue -
State: closed - Opened by trevex over 11 years ago
- 2 comments
#47 - Authentication of WebSockets with Session
Issue -
State: closed - Opened by trevex over 11 years ago
- 2 comments
#47 - Authentication of WebSockets with Session
Issue -
State: closed - Opened by trevex over 11 years ago
- 2 comments
#46 - Published artifact not compatible with Java 6
Issue -
State: closed - Opened by thoepfner over 11 years ago
- 13 comments
#46 - Published artifact not compatible with Java 6
Issue -
State: closed - Opened by thoepfner over 11 years ago
- 13 comments
#45 - Add tool to watch the file system for changes and run a build file
Issue -
State: closed - Opened by veebs over 11 years ago
- 1 comment
#45 - Add tool to watch the file system for changes and run a build file
Issue -
State: closed - Opened by veebs over 11 years ago
- 1 comment
#45 - Add tool to watch the file system for changes and run a build file
Issue -
State: closed - Opened by veebs over 11 years ago
- 1 comment
#45 - Add tool to watch the file system for changes and run a build file
Issue -
State: closed - Opened by veebs over 11 years ago
- 1 comment
#44 - Remove java code for NPN and concurrentlinkedhashmap
Issue -
State: closed - Opened by veebs over 11 years ago
#44 - Remove java code for NPN and concurrentlinkedhashmap
Issue -
State: closed - Opened by veebs over 11 years ago
#44 - Remove java code for NPN and concurrentlinkedhashmap
Issue -
State: closed - Opened by veebs over 11 years ago
#44 - Remove java code for NPN and concurrentlinkedhashmap
Issue -
State: closed - Opened by veebs over 11 years ago
#43 - v0.2.4 tidy up
Issue -
State: closed - Opened by veebs over 11 years ago
#43 - v0.2.4 tidy up
Issue -
State: closed - Opened by veebs over 11 years ago
#42 - Query String, Post Data and File Upload handing
Issue -
State: closed - Opened by veebs over 11 years ago
- 3 comments
#42 - Query String, Post Data and File Upload handing
Issue -
State: closed - Opened by veebs over 11 years ago
- 3 comments
#42 - Query String, Post Data and File Upload handing
Issue -
State: closed - Opened by veebs over 11 years ago
- 3 comments
#42 - Query String, Post Data and File Upload handing
Issue -
State: closed - Opened by veebs over 11 years ago
- 3 comments
#42 - Query String, Post Data and File Upload handing
Issue -
State: closed - Opened by veebs over 11 years ago
- 3 comments
#41 - Require a method to know when a websocket is ready to send message back to client
Issue -
State: closed - Opened by yuchangyuan about 12 years ago
- 12 comments
#41 - Require a method to know when a websocket is ready to send message back to client
Issue -
State: closed - Opened by yuchangyuan about 12 years ago
- 12 comments
#41 - Require a method to know when a websocket is ready to send message back to client
Issue -
State: closed - Opened by yuchangyuan about 12 years ago
- 12 comments
#41 - Require a method to know when a websocket is ready to send message back to client
Issue -
State: closed - Opened by yuchangyuan about 12 years ago
- 12 comments
#40 - Upgrade to Netty 3.5.7
Issue -
State: closed - Opened by veebs about 12 years ago
- 2 comments
#40 - Upgrade to Netty 3.5.7
Issue -
State: closed - Opened by veebs about 12 years ago
- 2 comments
#40 - Upgrade to Netty 3.5.7
Issue -
State: closed - Opened by veebs about 12 years ago
- 2 comments
#40 - Upgrade to Netty 3.5.7
Issue -
State: closed - Opened by veebs about 12 years ago
- 2 comments
#39 - Upgrade netty 3.5.6
Issue -
State: closed - Opened by veebs about 12 years ago
- 3 comments
#39 - Upgrade netty 3.5.6
Issue -
State: closed - Opened by veebs about 12 years ago
- 3 comments
#39 - Upgrade netty 3.5.6
Issue -
State: closed - Opened by veebs about 12 years ago
- 3 comments
#39 - Upgrade netty 3.5.6
Issue -
State: closed - Opened by veebs about 12 years ago
- 3 comments
#39 - Upgrade netty 3.5.6
Issue -
State: closed - Opened by veebs about 12 years ago
- 3 comments
#38 - Make StaticContentHandlerConfig immutable
Issue -
State: closed - Opened by veebs about 12 years ago
#38 - Make StaticContentHandlerConfig immutable
Issue -
State: closed - Opened by veebs about 12 years ago
#38 - Make StaticContentHandlerConfig immutable
Issue -
State: closed - Opened by veebs about 12 years ago
#38 - Make StaticContentHandlerConfig immutable
Issue -
State: closed - Opened by veebs about 12 years ago
#38 - Make StaticContentHandlerConfig immutable
Issue -
State: closed - Opened by veebs about 12 years ago
#37 - Logback web log namespace error
Issue -
State: closed - Opened by veebs about 12 years ago
#37 - Logback web log namespace error
Issue -
State: closed - Opened by veebs about 12 years ago
#37 - Logback web log namespace error
Issue -
State: closed - Opened by veebs about 12 years ago
#37 - Logback web log namespace error
Issue -
State: closed - Opened by veebs about 12 years ago