ra lookup

gstein:

svn_client_commit() needs to open a session with a repository. This
means calling our two public routines out of libsvn_ra:

  /* Load all available RA implementations. */
  SVN_ERR (svn_client_init_ra_libs (&ra_baton, pool));

  /* Get the plugin which handles my URL */
  SVN_ERR (svn_client_get_ra_library (plugin, ra_baton, URL, pool)

(Oops, we need to rename these routines if they live in ra now!)

Anyway: unlike the command-line client (which runs a single subcommand
and then quits), some future GUI clients will stay "active" for long
periods of time, running many svn_client_* routines.

My question is whether it's safe for each svn_client_* routine to
independently call the two routines above. Looking at the code, it
*seems* ok... I mean, there's nothing wrong with calling
apr_dso_load() if the library is already loaded, right?
Received on Sat Oct 21 14:36:25 2006