Greg Stein <email@example.com> writes:
> Another point about why 1-to-1 mapping of URL to resource is handy: caching
> proxies. Even though v67 and v73 might be the same, the proxy will still
> need to fetch it.
Hmmm... (see below)...
> > The client isn't really using that information; it doesn't get to
> > actually "know" the node revision number. It's just acting as an
> > information store for the server.
> > Although we do open ourselves up to
> > the possibility of poorly written clients which irresponsibly dissect
> > the supposedly-opaque version resource URL.
> We'll cover our butts quite a bit because other clients will want to use
> libsvn_client (or even libsvn_ra_dav). But your point is still valid.
> Even so... I happen to have no sympathy for those guys :-) F'em. :-)
Heh. I'm beginning to think using the node revision in the Version
Resource URL isn't so icko after all.
Greg S, your call, you understand the issues best here. Now that I'm
not longer confused between Version Resource URL and entries file
revision numbers, I feel less worried about what goes on the in the VR
Received on Sat Oct 21 14:36:19 2006