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

I don't think that works. Among other things, lots of Rails internals use
procs, which won't marshal. You'd basically need to proxy the entire parent
environment over DRb, which is just a bit crazy (and likely impossible),
don't you think?
-- Yehuda

On Thu, Jul 23, 2009 at 7:09 PM, Joel VanderWerf <[e-mail]>wrote:

> 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
>
>


-- 
Yehuda Katz
Developer | Engine Yard
(ph) 718.877.1325