Re: I-D ACTION:draft-ietf-ldup-lcup-04.txt

On Monday, March 10, 2003, at 11:18  AM, Kurt D. Zeilenga wrote:

> When I referred to a "state-based" system, I hoped it was
> obvious that I was referring to a system which maintained
> the current state of directory and meta information but
> did not maintain historical state information, in particular
> histories of state and/or content updates.  If this was
> unclear, I apologize.

Yes... the ldup documents use state-based to refer to systems
that store the historical information as state, rather than
log-based systems which store the historical information in a
change log.

Let's call your scenario 'no-history'. This is how I think a 'no-
history' session would work...

The client has a snapshot of the directory at some point. This
point is defined by the lcup cookie it received with the data.
The server is in a particular state, and knows nothing about
its previous states. When the client begins an lcup session
with the server it offers up its cookie. The server is unable
to determine the difference between the cookie point and
the current point so must therefore send everything. The
client now has a current snapshot and a new cookie.

Synchronization has been achieved, albeit rather inefficiently.

John