Hey,
>
>Lastly, if somebody *does* want to tackle a per-conn FS, then it needs to be
>keyed by the repository path (and stop and think before you say "key it by
>the UUID").
>
>A single connection can quite legally talk to multiple
>repositories on the server, so we need to account for that.
>
OK so I'm going to step into it here. On IRC I did stop and think and I
still got it wrong:-)
So I'd like some edu-ma-cation please.
And yes, I understand that you can't get a UUID without having the FS open.
Where I got confused is: I was under the impression (falsely I assume)
that the uuid came across
from the client to the server in every request.
So naively, I assumed you could implement the cache like so:
1. Get the uuid from the request.
2. look for existing repos object in a hash keyed by uuid.
3. If no repos object is found, open the repos and get the uuid. Store
repo object in hash with uuid as key.
4. A subsequent request would go looking for that uuid, find it and
reuse it.
I went and looked at mod_dav_svn and I see clearly that using the
repository path as the key makes sense. It's needed to open the FS. So
it makes sense that it would be the key.
But, I'm wondering: What is the UUID actually used for *today*?
gat
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jun 11 08:21:41 2003