From: Francis Cianfrocca <garbagecat10@...>
Date: 2006-05-09T09:36:53+09:00
Subject: Re: Considering Ruby For a Networking Application

------=_Part_46427_18087219.1147135010470
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Yes, you want your callbacks to return quickly. Spin a Ruby thread
otherwise. If it turns out that many users of Eventmachine face that issue
(such as doing a database call while processing a callback) then we'll look
at incorporating a thread-pool into Eventmachine. That would fit with the
goals of Eventmachine, which are performance/scalability, ease-of-use, and
feature-completeness for server implementations.

On 5/8/06, James Edward Gray II <james@grayproductions.net> wrote:
>
> On May 8, 2006, at 2:32 PM, Francis Cianfrocca wrote:
>
> > I'm glad you asked. Eventmachine is single-threaded. That's an
> > essential
> > part of its design.
>
> So my callbacks need to return reasonably quickly right?  So
> EventMachine can get back to processing input from other sockets.  If
> I need to do a long-running calculation, I should spawn a Ruby Thread
> for that.  Sound right?
>
> I'm very excited about working with you're library.  Thanks so much
> for answering my questions.  I'm sure I will have more at some point...
>
> James Edward Gray II
>
>
>

------=_Part_46427_18087219.1147135010470--