Voting starts in March for the Drupal Association Board election.
One of the big intended benefits from the Kernel work is the ability to use Http caching logic directly rather than implementing our own caching logic. The Kernel component includes a PHP-space implementation of an Http reverse proxy cache. We want to use that for all kernel-called page segments; that is, the entire page itself plus all of the sub-requests. The easiest way to do that is to move the kernel from the 'kernel' DI entry to some other entry, and then make the 'kernel' entry an instance of the HttpCache object, configured with a Store class of our own that saves stuff to the Drupal cache system.
For now, we should let the HttpCache use whatever logic it uses. We can refine it later after the pieces are in place.
Of course, we'll also want a way to disable that cache object when a site is running behind a real proxy cache like Varnish, which is going to be way faster anyway.
This probably needs to wait for
FAILED: [[SimpleTest]]: [PHP 5.4 MySQL] 77,294 pass(es), 14 fail(s), and 2 exception(s). View
FAILED: [[SimpleTest]]: [MySQL] 57,613 pass(es), 61 fail(s), and 10 exception(s). View
FAILED: [[SimpleTest]]: [MySQL] 54,163 pass(es), 45 fail(s), and 0 exception(s). View
FAILED: [[SimpleTest]]: [MySQL] 53,935 pass(es), 46 fail(s), and 0 exception(s). View
FAILED: [[SimpleTest]]: [MySQL] 40,346 pass(es), 48 fail(s), and 1 exception(s). View