AnyEvent recursive blocking wait with Plack
schmorp at schmorp.de
Thu Mar 8 15:02:46 CET 2012
On Thu, Mar 08, 2012 at 11:47:38AM +0000, Dirk Koopman <djk at tobit.co.uk> wrote:
> >Yes, if Plack strives to do that, then it has to think about all of these
> >things. If the lowest common denominator does not allow it, then Plack can't
> >implement it.
> That is *precisely* what Plack attempts to do.
In any case, to actually add something constructive,
the required behavior is part of the psgi spec:
> Many people have spent a lot of time on Plack, probably more people
> and more time than on AnyEvent.
I somehow doubt that, looking at placks changelog vs. anyevents changelog.
But hey, you are probably entitled to your claims :)
> Go to any perl workshop and there will be someone talking about some
> aspect or use case of Plack.
Just returned from the german perl workshop - no plack.
Not that this does in any way diminish plack's popularity or usefulness,
but maybe you should work more on being constructive regarding the OP's
problem rather than doing PR?
> >Well, if the Anyevent::HTTPD handler is the only one allowing that then
> >you are in trouble. If it's a standard feature supported everywehre,
> >then enjoy - if it's not documented well, you could always ask the Plack
> Why not use one of the many Plack (http://plackperl.org) compatible
> frameworks such as: Mojolicious (http://mojolicious.org) or Dancer
> (http://perldancer.org)? Both of these frameworks (for instance)
> allow web apps to query other web servers.
Isn't that exactly what he is using? He tried to use AnyEvent::HTTPD,
which to me looks as plack-compatible as the frameworks you mentioned, and
also allow web apps to query other web servers.
Do I miss something obvious?
The choice of a Deliantra, the free code+content MORPG
-----==- _GNU_ http://www.deliantra.net
----==-- _ generation
---==---(_)__ __ ____ __ Marc Lehmann
--==---/ / _ \/ // /\ \/ / schmorp at schmorp.de
More information about the anyevent