You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm experimenting using netpoller with tls and websocket (github.com/gobwas/ws/wsutil), and I am concerned that with larger messages, the nonblocking socket read will return less than is needed to complete the websocket frame? From what I found via google search, nonblocking is only necessary when using level triggering, yet netpoll sets nonblocking on all connections.
do you see any problem with making setNonBlocking as optional and do you envision any issue with github.com/gobwas/ws/wsutil framing on top of netpoll
The text was updated successfully, but these errors were encountered:
I'm experimenting using netpoller with tls and websocket (github.com/gobwas/ws/wsutil), and I am concerned that with larger messages, the nonblocking socket read will return less than is needed to complete the websocket frame? From what I found via google search, nonblocking is only necessary when using level triggering, yet netpoll sets nonblocking on all connections.
do you see any problem with making setNonBlocking as optional and do you envision any issue with github.com/gobwas/ws/wsutil framing on top of netpoll
The text was updated successfully, but these errors were encountered: