Re: svn_delta_path_driver(), its purpose and future

On 11/29/2011 04:56 PM, Hyrum K Wright wrote:
> It sounds very much like SDPD is simply a mechanism for doing with Ev1
> what Ev2 is explicitly designed for: operating on arbitrary paths in
> the delta tree. All SDPD does is fill in the gaps so that the sender
> doesn't have to worry about all the intermediate calls between the
> paths of interest, right?

Yup!

> I understand and expect that consumers of SDPD as currently
> implemented will need to use Ev1. The problem is that they don't take
> very kindly to instances where Ev1 is driven in an asynchronous mode,
> which doesn't technically violate the Ev1 API. But I think this is a
> problem that we can work around.

But ... but ... the code sites which are using SDPD *are* the drivers of the
editor, not the implementors.

Maybe you meant, "they don't take very kindly to instances where Ev1 doesn't
immediately return an error because all the real work is done by a nested
Ev2 in a big batch at the end of the Ev1 drive" ?

-- 
C. Michael Pilato <cmpilato_at_collab.net>
CollabNet   <>   www.collab.net   <>   Distributed Development On Demand