I've been working out a contradiction in web apps:

• it's nice for each page to be independent, without having to worry about changes from other enviroments
  
• it's nice to have just a few cached database connections
  

I can use continuations to make repeated ruby requests independent, but the problem is that I want a few objects to persist. Implementing something that will roll back modifications to Kernel while preserving a few database connections seemed daunting. Until I realized ... run the connections in a separate process and communicate using drb.

Update: Ara Howard has released a postgres connection pool