From: braver <deliverable@...>
Date: 2007-05-27T07:35:12+09:00
Subject: Re: querying persistent ruby objects in memory

On May 26, 2:24 pm, Robert Klemme <shortcut...@googlemail.com> wrote:
> I'd consider using Marshal.

That's just plain serialization, isn't it?  I've seen that and
Madelaine; but my wish is to keep the objects in memory without the
need to dump/reload it, however fast.  (That would be a last resort.)

The question is, can we keep an object in memory in one thread, and
explore/change it from another?  In the worst case, we can probably
quickly dump an object into a memory region and reload it back via
Marshal -- I guess a crude solution is forming here, using shared
memory or RAM disk -- have to see what's there for macs...  But still
I wonder what folks think in terms of all kinds of RAM persistence in
ruby solutions.

Cheers,
Alexy