[dancer-users] Non-blocking stuff
xsawyerx at gmail.com
Tue Jan 12 18:19:46 GMT 2016
Could you provide some sample code so I could play with it?
Also, how are you implementing the delayed server? What event loop are you
using? Are you trying to do fully non-blocking asynchronous or are you just
having a delayed response? There is a big difference.
The problem with delayed responses is that there are several options and in
between them you need to understand how they work, what they do, event
loop, the effect *on* your code, the effect *of* your code etc. That's why
it's a pretty advanced feature that is usually unnecessary and the usage of
it should probably be very well contained.
On Fri, Jan 8, 2016 at 5:55 PM, Andrew Beverley <andy at andybev.com> wrote:
> On Sat, 2016-01-09 at 00:09 +1030, David H wrote:
> > I'm not sure if there is a way (or if this even makes sense) to fork
> > out each request so the dancer site isn't just sitting there waiting
> > for the last thing to complete.
> Really stupid question, but I assume you do have Starman configured for
> multiple processes accepting requests on the server-side? Otherwise you
> would of course see the behaviour you describe.
> > I tried using the Delayed responses (Async/Streaming) listed here:
> I would expect that. Delayed is still single-threaded (?), it just
> allows responses to be sent part way through processing request (I
> think, I've not looked at it in detail).
> I certainly would have thought that Starman or other multi-threaded
> server is the way to go.
> I do have some resource-intensive processes in one of my apps (that
> produce data for the same webpage via a separate request), and I've
> never noticed a problem. I've never looked at it in detail though. I'm
> using fast-cgi in Apache.
> dancer-users mailing list
> dancer-users at dancer.pm
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the dancer-users