Re: [Httplib2-discuss] Non-opaque cache keys
Status: Beta
Brought to you by:
jcgregorio
From: Joe G. <jo...@bi...> - 2006-11-15 06:04:29
|
On 11/14/06, Sam Ruby <ru...@in...> wrote: > It looks like the current implementation takes the md5 of a somewhat > normalized URI and passes that as a key to the cache. > > For debug-ability and to increase the potential for integration with > other subsystems, I'd like to suggest that this be changed to pass > either the original URI unaltered or a normalized URI with the logic to > do the normalization refactored out into a separate function. This is a great idea, I was frankly jealous when I looked at the Venus cache and saw that it was filled with non-opaque named files. > Either way, the current FileCache could do the remaining > normalization/hashing of the key. Other storage systems could either > use the key as is, or could employ a different hash mechanism. That works for me, shouldn't take long to implement. Thanks, -joe -- Joe Gregorio http://bitworking.org |