[Date Prev][Date Next][Thread Prev][Thread Next][Author Index][Date Index][Thread Index]
Re: Notes on accessing past versions
- To: Benjamin Fallenstein <b.fallenstein@xxxxxx>
- Subject: Re: Notes on accessing past versions
- From: Tuomas Lukka <lukka@xxxxxxxxxx>
- Date: Fri, 2 Mar 2001 12:01:14 +0200
- Cc: ZZ Development <zzdev@xxxxxxxxxx>
- In-reply-to: <3A9F6E3A.786A3622@xxxxxx>; from b.fallenstein@xxxxxx on Fri, Mar 02, 2001 at 10:56:11AM +0100
- Mail-followup-to: Benjamin Fallenstein <b.fallenstein@xxxxxx>, ZZ Development <zzdev@xxxxxxxxxx>
- References: <20010223114609.A18335@xxxxxxxxxxx> <3A96DA92.FA0032F4@xxxxxx> <20010224115918.A32572@xxxxxxxxxxx> <3A9D5D73.9F2FC98@xxxxxx> <20010301161215.G25394@xxxxxxxxxxx> <3A9E7080.332EB496@xxxxxx> <20010302085954.D2918@xxxxxxxxxxx> <20010302101359.B17162@xxxxxxxxxxxxxx> <3A9F6E3A.786A3622@xxxxxx>
>
> * There must be one storage file for pull-outs. This means reading a
> space in must be done timestamp-by-timestamp: First, you execute a
> command in the pull-out file, then, commands in the other files, then
> you advance the timestamp a step, then you execute a command in the
> pull-out file...
Why a separate file? I think reading the file in in two passes would
be acceptable and probably simpler and less desynch-error prone.
But we have to first look at what the persistent data structure articles
have to offer.
Tuomas