HTTP v2: public API?

I met some corporate customers today who were wondering if we are
going to consider HTTP v2 to be a public API? We will have to support
the HTTP v2 protocol that gets deployed in 1.7 indefinitely so we will
always need to deal with backwards compatibility with 1.7 clients and
hence preserve that API, but are we going to make any guarantees about
the protocol for future versions? Are we going to make a statement
that the protocol is public or private just for svn's use and hands
off, do not use?

This hasn't been an issue with the svnserve protocol, but it's going
to be very easy to write a non-svn client that interacts with
Subversion using the new API.

Also, not that anyone has said this, but I don't think we should ever
drop the WebDAV protocol as there are shops out there that mount svn
for web developers or non-SCM aware departments for auto-versioning.
It's a feature we shouldn't loose.

Blair

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2364760
Received on 2009-06-24 03:29:39 CEST