[cap-talk] Persistence overview (was: Re: Styles of persistance)

[Jed Donnelley]

On 3/18/2008 12:20 AM, Bill Frantz wrote:
> capability at webstart.com (Jed Donnelley) on Sunday, March 16, 2008 wrote:
...
>>>> On Sat, 2008-03-15 at 16:40 -0700, Bill Frantz wrote:
>>>>> There may be a significant difference in the ease of object upgrade
>>>>> between systems that save the stack as part of the persistent state
>>>>> and systems that don't.
>> I'm afraid I don't understand the distinction you are referring to.
>> Can you explain...
> 
> An object system like Java...

I have to apologize somewhat for my message above (don't understand ...).

I wrote that message and then decided to not send it and do further
research.  Unfortunately I inadvertently ended up sending it by
mistake without further review.

Still, I found BillF's response helpful.

The main thing I'm trying to contribute in this thread
is to separate:

1.  The functionality of capability/object persistence and
     that functional value
[persistence with two "E"s and no "a", right?]

from

2.  Issues in implementing capability/object persistence.

My effort to define more exactly what we mean by persistence:

http://www.eros-os.org/pipermail/cap-talk/2008-March/010467.html

was where I intended to start #1.  I believe Bill's
"Styles of  persistence" thread focuses on #2.

I'll share some experience regarding implementing object/
capability persistence in the sorts of systems I've worked
on (mostly the capabilities as data NLTSS system) in
a separate message.

--Jed  http://www.webstart.com/jed/