On Fri, Apr 6, 2012 at 1:10 PM, Greg Stein <[email protected]> wrote: > > On Apr 6, 2012 2:05 PM, "Hyrum K Wright" <[email protected]> wrote: >> >> In case folks haven't been following commits@, there's been a bit of >> work on the ev2-export branch on implementing Ev2 drivers for commits. >> While we're not quite ready for it yet, at some point we'll need to >> start thinking about how to marshall Ev2 drives over the wire to >> waiting servers. As this design work is largely orthogonal to the >> current implementation efforts, and my familiarity with our existing >> protocols is pretty weak, I'd invite other folks to start thinking >> about these issues and discussing them here. > > Already ahead of you :-) > > I was going to suggest a new RA API rather than rev'ing get_commit_editor. > By going that route, the coding can occur on trunk, and we migrate as > appropriate, leaving the delta editor in place.
Yep, that's the same conclusion I reached a few days ago. ;) > This would be the new "commit plan, followed by drive" design we discussed. > > The new RA entrypoint(s) could even have a default implementation in ra/ > that would use the original delta editor. Thus, we don't even have to > implement the new interface for all layers. This is a possibility. The current commit_editor4() on the ev2-export branch wraps the Ev1 implementation using the shims. -Hyrum -- uberSVN: Apache Subversion Made Easy http://www.uberSVN.com/
