Hi guys!
Just wanted to mention the current state of the server side cache:
- It isn't prepopulated yet. I intend to do that tonight. I will then send email to those release owners that have faulty URLs (there are about 10.
- The checksum calculation (when it is triggered) and how it is used could need some adjustments. For example, a button to refresh the checksum could be nice. Today it is only triggered when changing the URL or adding a new release IIRC. So if you upload a file to SM, add a release (checksum calculated) and then re-upload the same file - then it will be wrong. And I admit I don't recall just now what the client says today if the checksum fails.
And right - about an MCRepository subclass - I would really want such a construct to operate on top of the local SM domain objects because from now on I intend to start working on the new "infrastructure" of SM (a distributed model).
regards, Göran
Avi Bryant avi.bryant@gmail.com wrote:
On Nov 27, 2005, at 2:50 PM, Yanni Chiu wrote:
BTW, could SqueakMap be made to appear as a Monticello HTTP repository? Although I prefer to have a local cache of the .mcz files, the resulting .mcm files are not portable to others. In some cases, the actual repositories are on squeaksource, and those _can_ be put into the .mcm directly.
If this were done right (a specific MCRepository subclass for SqueakMap), it could take advantage both of your local SqueakMap cache, and of SqueakMap's new server-side caching. We should definitely do this.
Avi