cache_key_genid is missing documentation, here is what I found out by analyzing the code:
This plugin allows you to use a Kyoto database to increase genid per hostname, hence expiring the cache for a full domain using the zero cost mechanism to set the genid in the cache key.
The additional overhead for the plugin is:
- Parse hostname from given url
- Check kyoto DB for genid for the given host [DB lookup]
- Set genid for the cache key dynamically
This plugin takes just one argument:
- The path to the genid kyoto DB
I presume GoDaddy uses this in combination with a purge plugin like remap_purge to write values to the Kyoto DB to expire whole domains.
cache_key_genid is missing documentation, here is what I found out by analyzing the code:
This plugin allows you to use a Kyoto database to increase genid per hostname, hence expiring the cache for a full domain using the zero cost mechanism to set the genid in the cache key.
The additional overhead for the plugin is:
This plugin takes just one argument:
I presume GoDaddy uses this in combination with a purge plugin like remap_purge to write values to the Kyoto DB to expire whole domains.