On Thu, Mar 9, 2017 at 3:02 PM, Руслан Закиров <r...@sports.ru> wrote:
> It's kind of strange a bit. AnyEvent is a single API on top of event loops > (libev, libuv, > pure perl loop, ...). Sure I can use AE's implementation instead of > uwsgi's default, > but it feels wrong. Instead of replacing uwsgi's ioloop it feels more > correct to teach > AE to use uwsgi's default ioloop. > Ok, async_loop() uwsgi has is not callbacks based, so I can not write AnyEvent::Impl::UWSGI on top of it. This loop maps events on FDs and timeouts on wsgi requests. Manages runqueue when events happen. Am I missing something? However, I believe it's possible to do the following: * use AE's loop * on every registered app's callback store wsgi_req/async core id * use ugreen context switcher before jumping into app's callback or into uwsgi What do you think? -- Руслан Закиров Руководитель отдела разработки веб-сервисов +7(916) 597-92-69, ruz @ <http://www.sports.ru/>
_______________________________________________ uWSGI mailing list uWSGI@lists.unbit.it http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
