Hi All, Thanks for your kind replies.
Looks like it is not feasible/possible to remove URL hash map solution completely.. However, storage optimization was another topic in our mind, which content hash can save the day. We are thinking this can be a nice feature if implemented. If anybody decide to implement please let us know. regards Saltuk ________________________________________ From: Rasim Saltuk Alakuş Sent: Wednesday, August 27, 2014 7:17 PM To: dev@trafficserver.apache.org; us...@trafficserver.apache.org Subject: generating hash from packet content Hi All, ATS uses URL hash for cache storage. And CacheUrl plugin adds some more flexibility in URL hashing strategy. We think of creating hash based on packet content and use it as the hash while storing and retrieving from cache This looks a better solution, so that URI changes won't hurt caching system. One immediate benefit for example if you cache YouTube , each request for same video can have different URL and CacheUrl plugin does not always provide a good solution. Also maintaining site based hash filters looks not an elegant solution. Is there any previous or active work for implementing content based hashing? What kind of problems and constrains you may guess. Is there any volunteer to implement this feature together with us? Kind regards Saltuk Alakuş
