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

RE: svn commit: r1657782 - /subversion/branches/reuse-ra-session/BRANCH-README

From: Bert Huijben <bert_at_qqmail.nl>
Date: Fri, 6 Feb 2015 13:55:21 +0100

> -----Original Message-----
> From: brane_at_apache.org [mailto:brane_at_apache.org]
> Sent: vrijdag 6 februari 2015 12:10
> To: commits_at_subversion.apache.org
> Subject: svn commit: r1657782 - /subversion/branches/reuse-ra-
> session/BRANCH-README
>
> Author: brane
> Date: Fri Feb 6 11:09:54 2015
> New Revision: 1657782
>
> URL: http://svn.apache.org/r1657782
> Log:
> On the reuse-ra-session branch: Documentation change: Instead of expecting
> clients to manage the lifetime of idle sessions, expect that the RA cache
> implementation will take care of that itself and hide the complexity
> from the API.
>
> * BRANCH-README:
> Remove todo item about svn_client_close_all_sessions.
> Add todo item about idle session expiry.

How do we expire idle sessions if a client only uses Subversion api's once a day?

I don't think we want to rely on timers or threads.

Before this is merged back I would really like some supported option to just close all sessions (perhaps including those to the working copy databases), without destroying the client context.

The context also caches credentials, etc.

In shared process environments such as Eclipse and Visual Studio where libsvn_client is indirectly used, we can't just always hold on to expensive/limited resources.

        Bert
Received on 2015-02-06 13:57:26 CET

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.