> I don't know if I can start on it right away, but I'm very interested > in helping with this. In particular, the establish_connection stuff > and the way connections are cached is not very friendly right now to > Java appservers where the connection pooling usually happens > underneath the covers. If possible I'd like to find a solution that > includes the possibility of opening and closing connections around > each request and/or transaction. Opening connections in the appserver > is cheap because it's just checking out/returning the connection to > the pool. Perhaps any work toward that goal can use a similar > abstraction -- then I can wholesale replace Rails' own connection pool > with one that connects directly to the Java connection pool.
I spoke about this a little in edinburgh, but connection_specification is just screaming for some kind of class to manage all that stuff instead of a bunch of class methods with conditionals. Even without any functional changes that code smells and should be made much easier to customise. Not to sound too 'enterprise' but a simple 'connection factory' would make most people's lives that much easier ;). -- Cheers Koz --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
