[PROPOSAL] Re: Is mod_dav_svn safe for use in a threaded MPM?

This discussion seems to have stalled, so how about a proposal?
I might work up a patch for this today, but if not, i can do it
next week.

- Introduce a new mod_dav_svn configuration directive,
  SVNActivitiesDB, e.g.

  <Location /a>
    DAV svn
    SVNPath /repositories/a
    SVNActivitiesDB /var/tmp/repository-activities/a
    AuthzSVNAccessFile /repositories/a/conf/authz
  </Location>

  This specifies a directory to use as the filename/contents
  activity-id/txn-name database.

  Administrators who wish to serve a network-mounted repository
  from multiple hosts can move the activities database to fast
  local storage, assuming they can guarantee session affinity
  across http connections (which is possible).

- If SVNActivitiesDB is not specified, default to using
  'dav-activities' under the repository directory, e.g.

  <Location /b>
    DAV svn
    SVNPath /repositories/b
    AuthzSVNAccessFile /repositories/b/conf/authz
  </Location>

  /a would use /var/tmp/repository-activities/a and /b would use
  /repositories/b/dav-activities .

- Stop creating <repo>/dav in svn_repos_create .

- Upon upgrading, <repo>/dav becomes dead weight. In the
  unlikely event that a client was just ending its connection
  when the server stopped and the server has restarted quickly
  enough for the client's next connection attempt to succeed,
  that client would get an activity error, and the user would
  have to restart the commit.

-- 
Eric Gillespie <*> epg@pretzelnet.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org