Re: Asynchronous delta editor and error handling

Tobias Ringström <tobias@ringstrom.mine.nu> writes:

> A simpler solution is to define the following "rules":
>
> 1. If a delta editor operation returns an error, the editor is dead
> (or wedged, or in an error state or whatever you want to call it).
>
> 2. When the delta editor is dead, further operations are ignored by
> the receiver (and the driver must call abort_edit since every
> other operation is ignored anyway).

Perhaps we should just define an editor to allow asynchronous
operations on a very small subset of functions.... in particular, just
open/add_file(), apply_txdelta(), and close_file(). Nothing else. If
we fail to transmit file1 (and don't realize it yet), that doesn't
affect our ability to transmit file2.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 25 15:30:37 2003