Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

REQ: full-duplex support #4

Closed
escmarvin opened this issue Nov 27, 2013 · 6 comments
Closed

REQ: full-duplex support #4

escmarvin opened this issue Nov 27, 2013 · 6 comments

Comments

@escmarvin
Copy link

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?

@agentzh
Copy link
Member

agentzh commented Nov 27, 2013

@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 :)

@xeoncross
Copy link

Any news on this?

@agentzh
Copy link
Member

agentzh commented Jun 15, 2014

@xeoncross I'll work on this soon :)

@agentzh
Copy link
Member

agentzh commented Jul 14, 2014

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.

@agentzh
Copy link
Member

agentzh commented Jul 14, 2014

Because @ashun has success in using the new duplex cosocket feature with this library, I'm closing this :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants
@agentzh @xeoncross @escmarvin and others