Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / ninjasource/Ninja.WebSockets issues and pull requests
#24 - Documentation of exceptions thrown
Issue -
State: open - Opened by lugehorsam over 2 years ago
- 3 comments
#23 - One or more errors occurred. (502 Bad Gateway) while connecting to Azure
Issue -
State: closed - Opened by enniobolondi over 3 years ago
- 6 comments
#22 - Unable to specify correct buffer size for ReceiveAsync
Issue -
State: closed - Opened by HeikoBoettger over 3 years ago
- 4 comments
#21 - Ninja.WebSockets.dll is no longer signed with a strong name key
Issue -
State: closed - Opened by ryanc1024 over 3 years ago
- 2 comments
#20 - Is this library support unity webgl platform?
Issue -
State: closed - Opened by orangeagain almost 4 years ago
- 2 comments
#19 - Invalid pointer address in attempting to use a pointer. Possible DNS issue ?
Issue -
State: closed - Opened by cocapasteque about 4 years ago
- 3 comments
#18 - Unable to connect using wss, works with ws
Issue -
State: closed - Opened by Lokeshbhatia93 about 4 years ago
- 9 comments
#17 - Custom PingPong implementation (server)
Issue -
State: closed - Opened by roiko about 4 years ago
- 4 comments
#16 - SSL support?
Issue -
State: closed - Opened by manijak almost 5 years ago
- 4 comments
#15 - What is the advantage of Ninja.WebSockets in comparison to WebSocket implementation from Microsoft?
Issue -
State: closed - Opened by msbasanth about 5 years ago
- 3 comments
#14 - Send message to a specific client
Issue -
State: closed - Opened by rsegovia about 5 years ago
- 5 comments
#13 - Question about data frame received after close
Issue -
State: closed - Opened by yingfangdu about 5 years ago
- 2 comments
#12 - Websocket ID?
Issue -
State: closed - Opened by justStand about 5 years ago
- 3 comments
#11 - One to many broadcast?
Issue -
State: closed - Opened by lboogs99 over 5 years ago
- 2 comments
#10 - fix(sign-assembly): strong-name sign assemblies
Pull Request -
State: closed - Opened by nimitr almost 6 years ago
- 3 comments
#9 - ConnectAsync throws exception when receiving "HTTP/1.1 101 Web Socket Protocol Handshake"
Issue -
State: closed - Opened by Flotto85 almost 6 years ago
- 4 comments
#8 - Ninja.WebSockets.dll is not a strongly named assembly.
Issue -
State: closed - Opened by yingfangdu almost 6 years ago
- 3 comments
#7 - Would like to use a custom JSON payload in PingPongManager
Issue -
State: closed - Opened by essenbee about 6 years ago
- 2 comments
#6 - How to use this?
Issue -
State: closed - Opened by LeXtruX about 6 years ago
- 3 comments
#5 - Need .Net 4.5 support.
Issue -
State: closed - Opened by yingfangdu about 6 years ago
- 3 comments
#4 - hand shake will fail if client has "Sec-WebSocket-Protocol" in the header
Issue -
State: closed - Opened by yingfangdu about 6 years ago
- 10 comments
#3 - The WebSocket implementation is not thread safe.
Issue -
State: closed - Opened by yingfangdu about 6 years ago
- 2 comments
#2 - Update README.md
Pull Request -
State: closed - Opened by mallibone about 6 years ago
- 1 comment
#1 - A few bits and pieces.
Pull Request -
State: closed - Opened by NimaAra over 6 years ago
- 9 comments