Re: SASL for ra_svn on Windows

Stefan Küng wrote:
> The problems I see with the Cyrus SASL lib are again the same as I had
> with the apr-iconv lib: dll hell.
> The plugin dlls are loaded from a fixed path and/or from paths specified
> in the registry. This will work as long as all plugins are built with
> the same c-runtime as the app using them. But only one app is needed
> which installs/overwrites the plugin dlls built with e.g. the crt v8
> (requires a manifest), and all apps built with older crts can't use them
> anymore.

AFAIK this is only a problem if you allocate memory (or any other C
runtime resource) in the main library and then try to free it in the
plugin, or vice-versa. If that is the case then we should be fine
because SASL follows a "if you allocate it, you free it" policy.

-- 
Vlad
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org