Re: [development] Object caching

Easy, we'd continue to maintain a URL alias table with all the path aliases. In the node/user/taxonomy object we'd just 'cache' the active path alias (duplication).

(I'm not claiming this is the best solution.)

Sounds like a legitimate case for de-normalization for performance. The tricky part is making sure that who ever updates one updates the other, so we stay consistent. This better be a function that is called and does the work behind the scene, and no one touches the raw tables.