Voting starts in March for the Drupal Association Board election.
Starting on line 95:
** * Constants defining cache granularity for blocks and renderable arrays. * * Modules specify the caching patterns for their blocks using binary * combinations of these constants in their hook_block_info(): * $block[delta]['cache'] = DRUPAL_CACHE_PER_ROLE | DRUPAL_CACHE_PER_PAGE; * DRUPAL_CACHE_PER_ROLE is used as a default when no caching pattern is * specified. Use DRUPAL_CACHE_CUSTOM to disable standard block cache and * implement * * The block cache is cleared in cache_clear_all(), and uses the same clearing * policy than page cache (node, comment, user, taxonomy added or updated...). * Blocks requiring more fine-grained clearing might consider disabling the * built-in block cache (DRUPAL_NO_CACHE) and roll their own. * * Note that user 1 is excluded from block caching. */
1. In the first example, what does it actually mean, in terms of Drupal caching, to use DRUPAL_CACHE_PER_ROLE | DRUPAL_CACHE_PER_PAGE? More examples are needed (look at error handling in php.ini for a good example of good documentation)
2. What is DRUPAL_CACHE_CUSTOM, and what am I supposed to do with it?
3. What's the difference between DRUPAL_CACHE_CUSTOM and rolling your own and DRUPAL_NO_CACHE and rolling your own?
|#27||drupal_cache_docs-863428-27.patch||1.94 KB||Albert Volkman|
PASSED: [[SimpleTest]]: [MySQL] 39,409 pass(es). View
|#24||drupal_cache_docs-863428-24.patch||2.2 KB||Albert Volkman|
PASSED: [[SimpleTest]]: [MySQL] 41,309 pass(es). View
|#24||interdiff.txt||2 KB||Albert Volkman|
|#22||drupal_cache_docs-863428-22.patch||1.17 KB||Albert Volkman|
PASSED: [[SimpleTest]]: [MySQL] 41,297 pass(es). View
|#19||drupal_cache_docs-863428-19.patch||1.6 KB||Albert Volkman|
PASSED: [[SimpleTest]]: [MySQL] 39,394 pass(es). View