sudheerv commented on pull request #7918: URL: https://github.com/apache/trafficserver/pull/7918#issuecomment-858258711
> I'm puzzled by the URL based tables. What are those needed for? If the counter is in the rule, that can be accessed via`UrlRewrite::MappingStore::hash_lookup`. For regular expression, those are a `Queue` which is a subclass of `DLL` which has iteration support. Why have yet another lookup structure? For regex, yes the rule is directly accessible via the list and that’s exactly what I’ve done in the patch. The problem is with the hash_lookup which is a hash table of type UrlPathMappingIndex - it has a trie representation of each path prefix, not sure how to walk through that trie - didn’t find any clean API to do that, hence added a separate table to walk through these non regex rules -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
