Justin Erenkrantz <email@example.com> writes:
> *raises hand*
> As some of you may already know, Google has hired me to work on
> Subversion with my main goal of integrating serf with Subversion.
> Google and I (since, well, I accepted!) both view this as an excellent
> opportunity to finally realize the ideas Greg and I have had for a
> long time about Subversion and serf. We can finally prove that DAV on
> the client-side doesn't *have* to be complicated and slow. We do hope
> that we'll be able to improve Subversion client's WebDAV performance
Great news, Justin.
> Due to obligations that I need to complete before I head to Google, I
> haven't sat down in detail and sketched out how it will all work out
> yet. I do know that I intend to create a new ra_serf layer (for lack
> of a better name) that will aim to replace ra_dav with Neon. The
> code-bases of neon and serf are too different to share the same ra
> layer on the client-side. (We'd likely make ra_serf/ra_dav a
> configure-time option - you'll get one or the other.) I also have
> some ideas for some other nifty features that we'll be able to add
> with serf that we can't do with neon as well.
Compile-time option sounds good.
The naming thing is a bit wierd... after all, they're both DAV. We
just didn't call the first one libsvn_ra_neon :-).
Is there any way to put both serf and neon implementations separately
inside libsvn_ra_dav/? I'm not proposing that we mix the code, just
that we keep the names reflective of the actual situation.
> If you have any general questions, please feel free to ask. If you
> want details about ra_serf, well, I don't know that just yet - that
> will have to wait until I have the time to answer it in the detail it
> merits. =) -- justin
Looking forward to January, and congratulations!
www.collab.net <> CollabNet | Distributed Development On Demand
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Mon Nov 28 02:10:12 2005