Storing Paths Related Question

Currently we store paths as the quite sensible string representation:
"/trunk/subversion/libsvn_fs/....".

However, can anybody think up useful/frequent access patterns where the
following representation might be more optimal, or make certain code
paths cheaper by being able to take advantage of such path storage? If
so, which code paths does this help?

/NR1.C1.T1/NR2.C1.T1/NR3.C1.T2/.....

Or to put the idea in abstract math like speak: an ordered sequence of
NodeRevisionPKs without any named attached to each NodeRevision.

Thoughts?

Bill

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jun 14 01:21:52 2002