[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Dependency versioning question

From: Greg Stein <gstein_at_gmail.com>
Date: Thu, 6 Jun 2013 12:43:16 -0400

On Wed, Jun 5, 2013 at 8:01 PM, Ben Reser <ben_at_reser.org> wrote:
> On Thu, Jun 6, 2013 at 12:50 AM, Greg Stein <gstein_at_gmail.com> wrote:
>> Within serf, we're thinking about new models for connection and
>> protocol handling. And bumping to 2.0 to make that happen. What is the
>> effect upon libsvn_ra_serf and svn in general?
>> My thinking is "no big deal". That upgrading to svn 1.9 (or 1.10 or
>> whatever) would require installation of serf 2.0. All svn APIs would
>> remain unchanged, per our own versioning guidelines (both source and
>> binary APIs).
> Provided that we haven't exposed any API details of serf in our
> interface that's not a problem. I believe the only dependency where
> we might run into such details would be APR since we do require the
> use of APR APIs in order to use our library.

I *do* want to switch serf over to pocore at some point (better
networking and pool mem free/reuse), but its disparate memory pool
system can still be managed using APR's pool cleanups. We shouldn't
see any leakage out of the RA API.

Received on 2013-06-06 18:43:52 CEST

This is an archived mail posted to the Subversion Dev mailing list.