Re: EventMachine with thread pool and thread spawn

[Eric Wong <normalperson-rMlxZR9MS24@public.gmane.org>]

"Lin Jen-Shin (godfat)" <godfat-hOE/xeEBYYIdnm+yROfE0A@public.gmane.org> wrote:
> This way, it might be easier for me to "rebase" on master.
> However, I guess it might be time to give up this approach.
> All tests passed except for t0106-rack-input-keepalive.sh,
> but I don't find a good way to make it pass.

> The key might be that pause/resume don't seem to work in
> EventMachine? And using tempfile to buffer the request
> might not be realistic.

Yeah, t0106 is a tough one given the EM interface.

Btw, has anybody sent a patch to the EM guys to allow this?
(I don't do C++)

> Another way would be... simply mark this model as not
> suitable for large chunk pipelined requests. At least it seems
> working fine on our production site.
> 
> What do you think?

That's probably fine.

> Thanks for all your listening.
> 
> (Maybe it's really time to move forward to celluloid-io,
> not sure if I would get the chance to work on and finish it though..)

Fwiw, nowadays my personal take these days is to avoid EM/libev*-style
wrapper library unless they expose (or only have :P) a oneshot interface
(EPOLLONESHOT/EV_ONESHOT).  This is *especially* the case (for me) when
mixing epoll/kqueue with threads.

Standard event-triggered and level-triggered interfaces are both too
confusing to me.  Maybe it's just me, though :x
_______________________________________________
Rainbows! mailing list - rainbows-talk-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org
http://rubyforge.org/mailman/listinfo/rainbows-talk
Do not quote signatures (like this one) or top post when replying