[ruby-core:24539] Re: Proposal: savepoints

Yehuda Katz wrote:
> I have been thinking a lot about trying to find a way to make it easier 
> to implement code reloading in Ruby. Rails already implements code 
> reloading using remove_const, undef, etc., but it's fairly messy and can 
> produce problems. It's also a fair bit of code to implement.

What about splitting your code over drb?

Keep persistent stuff, such as sockets, db/file handles, in the drb 
server, which stays up.

Keep "user" code in the drb client, and restart for each code reload.

For the development version, mock up an interface for the client that 
looks like sockets, db handles, etc., but uses drb.

-- 
       vjoel : Joel VanderWerf : path berkeley edu : 510 665 3407