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

AE:: / EV:: compatible interface #6

Closed
zzzcpan opened this issue Jan 29, 2012 · 4 comments
Closed

AE:: / EV:: compatible interface #6

zzzcpan opened this issue Jan 29, 2012 · 4 comments

Comments

@zzzcpan
Copy link
Owner

zzzcpan commented Jan 29, 2012

Since nginx 1.1 is going stable soon ( http://trac.nginx.org/nginx/roadmap ) it makes sense to consider implementing partial support for AE::. It's probably going to be just AE::io and AE::timer. Some things won't ever work, like blocking wait (condvars) and signal handling. So it's just for IO.

@zzzcpan
Copy link
Owner Author

zzzcpan commented Mar 20, 2012

I'm closing this issue. There will be some low-level access but it won't be compatible with AE, sorry guys.
Nginx has a simple abstraction for each connection (ngx_connection_t) which allows it to send and receive data transparently over SSL, detect stale events and so on. AE doesn't have this. So it has to be a higher-level abstraction.

@zzzcpan zzzcpan closed this as completed Mar 20, 2012
@chenryn
Copy link

chenryn commented Jan 12, 2014

so there is no way to use async CPAN module inside nginx-perl? We must rewrite nginx-perl special module for everything?

@zzzcpan
Copy link
Owner Author

zzzcpan commented Jan 12, 2014

Yes, you are correct. But I wouldn't advice you to use nginx-perl for something complex anyway. It's ok for quick solutions and really hard for anything more.

@chenryn
Copy link

chenryn commented Jan 12, 2014

O...then it's make no sense because there is ngx_lua and the original nginx
perl module is enough for quick solutions.

2014/1/12 zzzcpan notifications@github.com

Yes, you are correct. But I wouldn't advice you to use nginx-perl for
something complex anyway. It's ok for quick solutions and really hard for
anything more.


Reply to this email directly or view it on GitHubhttps://github.com//issues/6#issuecomment-32124617
.

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

2 participants