Flexibility for fast_cache?
| Project: | Cache Router |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
First of all, amazing work here Steve. Hats off.
Secondly, and more specifically, I love the inclusion of DRUPAL_BOOTSTRAP_EARLY_PAGE_CACHE support.
I'm working on designing some systems that use frequent xhttpd requests to maintain a live "state", and scaling them effectively beyond a single server means putting the state request into a memcache cloud. Currently I have my own interface to that as a standalone php file, but being able to run that off the EARLY_PAGE_CACHE should (in theory) let me keep that stuff inside Drupal and get about the same performance.
I can do this now, but I'm restricted to using the cache_page bin and having everything work off uris.
Any thoughts or interest in adding a bit of architecture here to extend the fact_cache part of the system so it can be exposed to more bins and other rule sets? My initial thought is to allow fast_path to define an array of other callbacks to check if the base page_cache_fastpath() comes up false...

#1
Hmm... maybe not as important. The gap in performance between a dedicated state.php handler and fast_cache is pretty wide, unfortunately. I'll do some more testing, but it looks like this may not be as big a win as I thought.
#2
#3
Automatically closed -- issue fixed for 2 weeks with no activity.