Hi,
The user hit the cancellation button because he seems that the request
failed.
It would be irrelevant to Rails, and expensive execution is always
dangerous for any web applications.
2007/2/22, Jacob Hookom <jacob_at_hookom.net>:
> What is your interpretation of the difference between the 'user
> interface' and the 'web application framework' in the case Obie presented?
>
> TAKAI Naoto wrote:
> > Hi Jacob,
> >
> > IMO, the problem Obie pointed out is not the problem of web
> > application framework, but user interface.
> >
> > Anyway, in the context of JRuby on Rails, Rails is not MT-safe, so one
> > ruby instance is needed per request. Currently, JRuby on Rails solves
> > this problem by using object pool. If object pool is exhaused, JRuby
> > on Rails simply give up and return 503 error.
> >
> > Is this an answer to your question?
> >
> > Regards,
> > --
> > TAKAI, Naoto / takai_at_recompile.net
> >
> >
> > 2007/2/22, Jacob Hookom <jacob_at_hookom.net>:
> >> http://www.jroller.com/page/obie?entry=expensive_operations_especially_dangerous_in
> >>
> >>
> >> Any leg up on this with JRuby on Glassfish/Grizzly?
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> >> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
> >>
> >>
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>
--
TAKAI Naoto / takai_at_recompile.net