Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / cettia/cettia-protocol issues and pull requests
#19 - Add the version protocol header
Issue -
State: closed - Opened by flowersinthesand over 7 years ago
- 2 comments
#18 - `http.globalAgent.maxSockets` doesn't need to be touched
Issue -
State: closed - Opened by flowersinthesand over 7 years ago
#18 - `http.globalAgent.maxSockets` doesn't need to be touched
Issue -
State: closed - Opened by flowersinthesand over 7 years ago
#17 - Support Node 6/7
Issue -
State: closed - Opened by flowersinthesand almost 8 years ago
#16 - Drop support for Node 0.12
Issue -
State: closed - Opened by flowersinthesand almost 8 years ago
#15 - Update dependencies
Issue -
State: closed - Opened by flowersinthesand almost 8 years ago
- 1 comment
#14 - Update uuid to version 3.0.0
Pull Request -
State: closed - Opened by marcbachmann about 8 years ago
- 1 comment
#13 - Move heartbeat implementation from socket to transport
Issue -
State: open - Opened by flowersinthesand over 8 years ago
- 1 comment
#12 - Server option object
Issue -
State: closed - Opened by flowersinthesand over 8 years ago
- 2 comments
#11 - Add README.md
Issue -
State: closed - Opened by flowersinthesand over 8 years ago
#10 - Accept typed arrays in send method
Issue -
State: closed - Opened by flowersinthesand over 8 years ago
#9 - Binary event
Issue -
State: closed - Opened by flowersinthesand over 8 years ago
- 2 comments
#8 - Support Node 4+
Issue -
State: closed - Opened by flowersinthesand almost 9 years ago
#7 - Prefix query parameter representing protocol header with protocol name.
Issue -
State: closed - Opened by flowersinthesand over 9 years ago
- 1 comment
#6 - WebSocket transport doesn't work with URI whose authority has no trailing slash and query is not empty
Issue -
State: closed - Opened by flowersinthesand over 9 years ago
#5 - A client socket stays in connecting state if an invalid URI is given
Issue -
State: closed - Opened by flowersinthesand over 9 years ago
#4 - abort request kills the process if it throws an error
Issue -
State: closed - Opened by flowersinthesand over 9 years ago
#3 - WebSocket transport doesn't fire close event when a connection fails
Issue -
State: closed - Opened by flowersinthesand over 9 years ago
#2 - HTTP response's status code should be checked if it is 200
Issue -
State: closed - Opened by flowersinthesand over 9 years ago
#1 - Offline application
Issue -
State: closed - Opened by flowersinthesand over 9 years ago
- 4 comments