[Rails] Re: Re: Database Concurrency Without a Web Server?

snacktime
Thu, 13 Jul 2006 19:16:13 -0000

On 7/13/06, Francis Cianfrocca <garbagecat10@gmail.com>
wrote:
> snacktime wrote:
> > On 7/12/06, Francis Cianfrocca <garbagecat10@gmail.com> wrote:
> >>   # You initiate a database operation here...
> >> event-machine, but the result block would be called on the main
> >> event-machine thread as an event like any other.
> >>
> >> Comments?
> >
> > I think a thread pool for running code that will block is a great idea
> > while you are still working on all the different io handlers.  Say
> > someone is using it for network connections which are already
> > nonblocking, but also needs database or file access.  They can use
> > threads for the stuff that isn''t yet nonblocking.
> >
> > Good to see an event framework started for ruby, it definitely needed
> > one.
>
> EventMachine is definitely intended to meet the needs addressed by
> Twisted. What other features do you think are high on the list? Also,
> can you think of any applications that would be easier to write with
> such a Ruby framework?

Maybe something like twisted has where you can specify two methods to
a callback, one for success and one if there is an error so you can
catch it.