issues
search
fukamachi
/
websocket-driver
WebSocket server/client implementation for Common Lisp
BSD 2-Clause "Simplified" License
103
stars
27
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Emit a socket closed event in a non-async socket loop
#67
SuperDisk
closed
2 months ago
2
When closing a connection, the thread to be destroyed cannot be the current thread
#66
anranyicheng
closed
2 months ago
1
fix Commit https://github.com/fukamachi/websocket-driver/commit/228efcae0833a567fe446a5be8b573f9099ca0a6
#65
anranyicheng
closed
2 months ago
3
Support responding to html/socket on the same uri/port.
#64
Islam0mar
closed
1 year ago
1
Define conditions for threads to die on their own
#63
nyx-land
closed
1 year ago
2
server does not emit `:close` or `:error` when client disconnects without close frame
#62
samuel-hunter
opened
2 years ago
4
fix the double trigger when closing connection
#61
anranyicheng
closed
2 years ago
2
fix client close-connection function
#60
anranyicheng
closed
2 years ago
1
Client side 'close-connection' doesn't trigger on-close of server side
#59
nutora
opened
2 years ago
2
Replace ironclad dependency with babel and sha1
#58
samuel-hunter
closed
2 years ago
1
Replace clack-socket requirement?
#57
snunez1
opened
3 years ago
0
Remove trivial-utf-8 as a dependency
#56
samuel-hunter
closed
3 years ago
1
Do you plan to fix the double trigger on the close connection event soon?
#55
eko234
closed
3 years ago
1
Set fixed client port
#54
Ecsodikas
opened
3 years ago
1
Does this server work with large messages on Chromium?
#53
charJe
opened
4 years ago
0
How do I connect to wss?
#52
cynseok
opened
4 years ago
1
HANDLER-CASE causes loops
#51
phoe
opened
4 years ago
1
Do not use CL+SSL with Lispworks
#50
joelreymont
closed
9 months ago
0
close-connection causes websocket read thread to spin and use 100% CPU
#49
eeeeeta
opened
4 years ago
0
Replace ironclad with babel and sha1
#48
naryl
opened
4 years ago
4
error:1409442E:SSL routines:ssl3_read_bytes:tlsv1 alert protocol version
#47
erjoalgo
closed
4 years ago
1
unified closing handshake for client and server.
#46
petelliott
opened
5 years ago
2
close-connection on client does not send close frame
#45
petelliott
opened
5 years ago
0
make-client: additional-headers has no effect
#44
petelliott
closed
5 years ago
0
fixed close not being sent
#43
petelliott
closed
5 years ago
0
client close event triggered twice when server closes connection
#42
petelliott
opened
5 years ago
0
client sees close reason as an integer vector rather than a string.
#41
petelliott
closed
5 years ago
1
fixed close not being sent on close-connection
#40
petelliott
closed
5 years ago
0
server does not close connection.
#39
petelliott
closed
5 years ago
1
Emit errors on disconnection
#38
ralt
opened
5 years ago
3
Version can be a string
#37
knobo
closed
6 years ago
1
Quicklisp load issue for websocket-driver-client
#36
scoofry
closed
6 years ago
1
Making sending from a separate thread work when using Woo as a backend server
#35
svetlyak40wt
opened
6 years ago
10
Immediately quits when using Hunchentoot/LispWorks 7.1
#34
manuel
closed
6 years ago
2
Fixed inconsistent params on "close" event
#33
kkazuo
closed
6 years ago
1
Adding ca-path argument in start-connection function
#32
LeafChage
closed
5 years ago
1
README: add `close-connection' to the code snippet
#31
uint
closed
6 years ago
1
SSL: Add a way to skip local cert verification on connecting
#30
uint
closed
6 years ago
1
Can't redfine WS handlers w/ SLIME
#29
duncan-bayne
closed
6 years ago
2
rejecting a connection
#28
aarvid
opened
6 years ago
0
Fix emitting close on write error
#27
knobo
closed
7 years ago
0
Providing special bindings when creating a thread
#26
vendethiel
opened
7 years ago
0
Close/events on woo.ev.tcp:*connection-timeout*
#25
knobo
opened
7 years ago
1
upgrade on: "connection" = "keep-alive, Upgrade"
#24
knobo
closed
7 years ago
2
(wsd:on :close ws) message does not fire when browser closes.
#23
knobo
closed
7 years ago
7
Closoing connection
#22
knobo
closed
7 years ago
1
Should close-connection be called when closing the connection?
#21
knobo
closed
7 years ago
1
:close callback has different arguments than documented
#20
vozhyk-
closed
6 years ago
3
Disable x509 location verification
#19
vendethiel
closed
5 years ago
5
Trouble figuring out where the code for :on :message is located
#18
pebblexe
closed
7 years ago
1
Next