-
Notifications
You must be signed in to change notification settings - Fork 111
REQ: full-duplex support #4
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
@escmarvin Yes, this is planned. Actually @aviramc has contributed a patch that allows a "light thread" to read a cosocket object while another "light thread" is writing to it: openresty/lua-nginx-module#290 I'm still reviewing @aviramc's patch and it's expected to get merged soon :) |
Any news on this? |
@xeoncross I'll work on this soon :) |
Just FYI, the latest OpenResty 1.7.2.1 formal release already includes the full-duplex cosocket API by default (via ngx_lua 0.9.10). It's worth mentioning that it is not recommended to use ngx_lua 0.9.9 though because it contains a bad regression that could lead to memory leaks in a special case. If you really want to use a standalone ngx_lua module instead of the openresty bundle, then use at least ngx_lua 0.9.10 instead. |
Because @ashun has success in using the new duplex cosocket feature with this library, I'm closing this :) |
As far as I can tell there is currently no way to act upon events and send packets from the server to the clients? - Is this a planned feature?
The text was updated successfully, but these errors were encountered: