joaotavora / hunchensocket

RFC6455 compliant WebSockets for Common Lisp

joaotavora/hunchensocket Issues

Some systems failed to build for Quicklisp dist
Updated 2 years ago
websocket.org is no longer available, can not test the echo service as shown in the README
Updated 2 years ago
Websocket server without hunchentoot?
Closed 3 years ago1
How to stop WebSocket Server?
Updated 4 years ago13
"I/O timeout while doing input on #<SB-SYS:FD-STREAM" on unexpected connection close
Updated 4 years ago6
Blocking behaviour
Closed 4 years ago4
pending opcode is not reset properly
Updated 4 years ago3
capability to send message to server via onopen and onclose?
Closed 5 years ago2
The single socket "activity timeout" isn't working like it should. Two independent timeouts aren't being reset every time a single read/write happens.
Updated 6 years ago20
option to trap/ignore broken pipe error on unexpected connection close
Closed 6 years ago1
"Recursive lock attempt" on unexpected connection close
Closed 6 years ago1
FLEXI-STREAMS:OCTETS-TO-STRING in HANDLE-FRAME taking 20%
Closed 6 years ago7
support receiving binary messages
Closed 6 years ago2
more explicit explanation
Updated 6 years ago1
Can hunchensocket and hunchentoot share the same port?
Updated 6 years ago5
hunchensocket close connection after 300s
Closed 7 years ago1
while define subclass of websocket-client, how does `(name :initarg :user-agent)` work?
Closed 9 years ago5
Disconnect by client won't notify server
Closed 9 years ago7
Cannot send messages longer than 13 characters
Closed 10 years ago2
Example code breaks when message too long, completely breaks when unexpectedly closing tab
Closed 10 years ago4
Error reporting is poor
Updated 10 years ago