Re: Ev2 RA protocols

On Apr 6, 2012 2:05 PM, "Hyrum K Wright" <hyrum.wright_at_wandisco.com> 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.

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.

Cheers,
-g
Received on 2012-04-06 20:11:27 CEST