That would also let us save bandwidth by not downloading files already sitting in the client's package cache.
How so? Isn't the package-cache checked before hitting the server at all? It certainly should be.
No, it's not. Currently that's not possible, because different files can have the same name. And currently we have no way to tell them apart.
Even still, we could check the package-cache first, open up the one with that name and see if its teh correct UUID...
No. No two MCZ's may have the same name, certainly not withiin the same repository, because MCRepository cannot support that. So maybe we need project subdirectories under package-cache to properly simulate each cached Repository. I had no idea we were neutering 90% of the benefits of our package-cache because of this too, and just sitting here, I can't help wonder whether this is why MCProxy doesn't work properly either!
The primary purpose of a cache is to *check it first* to speed up access to something, right? What you say about package-cache sounds really bad we should fix that, not surrender to it.
- Chris