On Feb 14, 2007, at 10:17 AM, Frank Barknecht wrote:
> Hallo,
> Roman Haefeli hat gesagt: // Roman Haefeli wrote:
>
>> the state saving is more a side effect, since the main goal was to
>> provide a system, that makes sure, that all patches have the same
>> state,
>> no matter when a user join
Hallo,
Roman Haefeli hat gesagt: // Roman Haefeli wrote:
> the state saving is more a side effect, since the main goal was to
> provide a system, that makes sure, that all patches have the same state,
> no matter when a user joins a running session. since that was
> implemented, it was very easy
hello
some notes about the state saving system used by netpd:
the state saving is more a side effect, since the main goal was to
provide a system, that makes sure, that all patches have the same state,
no matter when a user joins a running session. since that was
implemented, it was very easy to
Since it is an ever returning subject maybe its good to have a
summarized topic for this.
Could someone just give a list of existing "state-saving"-systems and
describe pro's and con's and the state of complexity ?
i think that could be very helpful for beginners ;-)
Thanks
Luigi
__