\On 5/29/07, Robert Egglestone <[EMAIL PROTECTED]> wrote: > That said, I don't feel that having a single generic ruby servlet and > trying to leverage it for a variety of purposes is necessarily the best way > to go. I'd much rather see a variety of tools (e.g. to manage runtimes), > which can be utilized by servlets for handling different situations, such as > RoR apps, or servlets implemented entirely in Ruby. This is because we've > already seen on the mailing list that people have a variety of different > ways in which they want to combine Ruby with servlets, different URL > schemes, and so forth, and it would be good to have different servlets for > these different situations.
I agree. Inheritance is not necessarily the best approach to reuse. I think there is stuff in GoldSpike that can be extracted out into some form of "commons". Things like the Rails pool and the context listener. The Rails instance pool is useful even outside servlets, what about an EJB implemented using Rails? Scary thought indeed, but could be very useful if you need to build a SOAP web service or a message driven bean. Or what about a Spring bean implemented with Rails? etc. etc. Getting the Rails pool right is tricky as there's plenty of threading involved, right now there's something shaky with it but I can't quite work out what it is. Solving those kind of problems in a generic package that can be reused across usage scenarios would be very useful. Might not be that much code, but with threading it's all in the details. _______________________________________________ Jruby-extras-devel mailing list [email protected] http://rubyforge.org/mailman/listinfo/jruby-extras-devel
