[cap-talk] Handling upgrade with the Waterken Server
david.hopwood at industrial-designers.co.uk
Fri Jan 25 06:52:31 EST 2008
Bill Frantz wrote:
> tyler.close at gmail.com (Tyler Close) on Sunday, January 20, 2008 wrote:
>> I think a common theme across many design patterns for handling
>> upgrade will be to dodge the problem as much as possible. For example,
>> one approach is to design a set of classes whose sole purpose is to
>> hold your long-lived state. These objects are kept as simple and
>> generic as possible.
> Traditionally these objects are files and directories. Thus you
> have described the approach used by Unix, MacOS, Windows etc.
More precisely, the approach used by Unix, MacOS, Windows etc. is a
special case of what Tyler described. Note however that links in a
Unix-like filesystem are not capabilities, and cannot directly be used
to emulate them.
More information about the cap-talk