Here is my D7 plan now is to solve path aliases, loosely based on what kkaefer did for CSS and JS for NP (which might be released). On every (or every N?) page load, dump the paths that are aliased to a statistics table for a given page -- this is speedy with INSERT DELAYED. On every M page load, pick up the top X percent of those and cache the bunch for the page. This way, the dynamic links in say, blocks won't be cached opposed to the current patch in the Drupal issue queue which caches on every page load effectively making the cache useless for any dynamic site.
Commenting on this Story is closed.
I'm not quite seeing how this fixes the problem if, for example, I have 100 links on a page, and only 10 have aliases. I will still attempt to look up at least 90 on every page load, right? Or is this cache going to hold all links on a page, with NULL or some other indicator of non-aliased links?
If you need to get an accession in a school, college or a university or call for any help in any kind of chore, so don’t get nervous. Buy papers about at narrative essay writing services. I don’t consider that there is anything dishonest in using writing services.