Short query: is this possible?
Hyrum has been doing some heavy lifting on moving our code to Ev2 for
commits. That work can be merged soonish, but a strong argument can be made
for "only when all RA providers have an Ev2 commit editor" (because
otherwise poor-perf shims are used). ra_local already has the needed
editor, and I've been doing work on ra_serf to stabilize a base for writing
the Ev2 editor. Somebody is going to need to write an editor for ra_svn. My
query/suggestion is to delete ra_neon rather than needing to write an
editor for it.
We can also choose to not move to an Ev2 commit editor at this time.
Somebody could also write the editor. We could also state the shim usage is
acceptable (not that scary, actually). My proposed option is to delete
ra_neon rather than write a lot of code for it.
So as a discussion point, is deletion possible? What are the potential
blockers? If we don't do this for 1.8, would we *ever* do this? What are
We have some issues filed against ra_serf. Which of them should be
considered as blockers?
A following question asks about API compatibility. I believe we can simply
sub ra_serf into any loader/query for ra_neon. Hard linkage to the ra_neon
library may also need a solution (it becomes a shim?).
Finally, another answer is to abandon ra_serf entirely, or to sign up for
dual HTTP provider maintenance in perpetuity.
I think that I have laid out our options, but have likely missed some.
Thoughts? Where/how do we proceed?
Received on 2012-05-16 12:47:09 CEST