RE: Merge ra-reuse-session branch to trunk or not?
From: Bert Huijben <bert_at_qqmail.nl>
Date: Sat, 19 Sep 2015 21:17:40 +0200
You wouldn't be able to check the id of the old auth baton once the pool is cleaned...
Libsvn_client could do some magic but this would have to be done in every place where we create/fetch Ra sessions. This makes it even more of a hack than the current code, while the idea was to clean things up by moving some of the code in the Ra sessions.
It is possible to attach a pool cleanup handler to see when the auth baton is cleared, but I don't like that solution either.
I agree with Ivan: We should check if the javahl trickery is valid. (We can fix javahl of course, but perhaps other users do the same thing)
We probably never described limitations...
Ivan Zhakov <ivan_at_visualsvn.com> writes:
> Otherwise, here are my ideas at the moment:
As a random idea:
4. Make each svn_auth_baton_t have a unique ID generated upon creation with
This is an archived mail posted to the Subversion Dev mailing list.