You are here

Home » API reference » Boost 5

TODO.txt in Boost 5

Same filename and directory in other branches
  1. 6 TODO.txt
This is a listing of known bugs, features that mostly work but are still
somewhat in progress, features that are being considered or planned for
implementation, and just miscellaneous far-out ideas that could, in
principle, be implemented if one had the time and inclination to do so.

(NOTE: there is no guarantee any of these items will, in fact, be
implemented, nor should any possible scheduling indications be construed as
promises under any circumstances. TANSTAAFL. If you absolutely need
something implemented right now, please contact the developers to see if
they're available for contract work, or if perhaps a modest donation could
speed things along.)

TODO: IN THE WORKS
------------------
* Finish up administration interface for pre-generating static files for all
  pages on the Drupal site in one go.
* Test interaction with other modules that also make use of ob_start().

TODO: FUTURE IDEAS
------------------
* Add a node-specific cache lifetime setting.
* Add admin-visible block for updating the cached copy of the current page.
* Other web servers than Apache are not supported at the moment. This is due
  to the way the cache dispatch is implemented using Apache mod_rewrite
  directives in the .htaccess file. Lighttpd support would be desirable but
  is not a high priority for the developer at present.
* User-specific static page cache. Could conceivably be implemented based
  on the existing user-cookie mechanism, though security would be a concern.
* Don't delete the entire file system cache when Boost is disabled; just
  rename the site's cache directory with the suffix `.disabled', speeding up
  cache regeneration once the module is re-enabled?

File

TODO.txt
View source 
  1. 

  2. This is a listing of known bugs, features that mostly work but are still

  3. somewhat in progress, features that are being considered or planned for

  4. implementation, and just miscellaneous far-out ideas that could, in

  5. principle, be implemented if one had the time and inclination to do so.

  6. 

  7. (NOTE: there is no guarantee any of these items will, in fact, be

  8. implemented, nor should any possible scheduling indications be construed as

  9. promises under any circumstances. TANSTAAFL. If you absolutely need

  10. something implemented right now, please contact the developers to see if

  11. they're available for contract work, or if perhaps a modest donation could

  12. speed things along.)

  13. 

  14. TODO: IN THE WORKS

  15. ------------------

  16. * Finish up administration interface for pre-generating static files for all

  17.   pages on the Drupal site in one go.

  18. * Test interaction with other modules that also make use of ob_start().

  19. 

  20. TODO: FUTURE IDEAS

  21. ------------------

  22. * Add a node-specific cache lifetime setting.

  23. * Add admin-visible block for updating the cached copy of the current page.

  24. * Other web servers than Apache are not supported at the moment. This is due

  25.   to the way the cache dispatch is implemented using Apache mod_rewrite

  26.   directives in the .htaccess file. Lighttpd support would be desirable but

  27.   is not a high priority for the developer at present.

  28. * User-specific static page cache. Could conceivably be implemented based

  29.   on the existing user-cookie mechanism, though security would be a concern.

  30. * Don't delete the entire file system cache when Boost is disabled; just

  31.   rename the site's cache directory with the suffix `.disabled', speeding up

  32.   cache regeneration once the module is re-enabled?