Skip to content
vicb edited this page Mar 11, 2012 · 8 revisions

Goal

The idea is to put some infrastructure in place for when the Cache Component will be ready. The first goal should to be able to configure memcache & memcached backends. If we can get this clean then adding new backends should be fairly simple.

Once the interface is stabilized we should start working on plugging the bundle wherever caching is used in the framework.

Code

  • Tune the configuration (BE & providers)

    • type should be optional for providers using BE defined in the config
  • Create the cache service, a repo for BE & providers, lazy-loading

  • Provide an xsd

  • Create, add and organize unit tests

  • Add support for commands (clear the cache)

  • Implement a cache collector (see StashBundle)

  • Ability to use several backends for a provider (Multiple in Stash)

  • Add classes to be compiled (per backend / provider ?)

  • Add more backend & provider factories (once memcache & memcached are stable & tested)

  • List places where the cache Bundle / component should be plugged

    • Annotation,
    • Validation,
    • DoctrineBundle,
    • Session,
    • Profiler storage,
    • Security ACL,
    • HTTP cache,
    • ... ?
  • Update the code to make use of the CacheBundle (should we keep BC ? provide adapters ?)

  • Update the CacheBundle to match the Cache component

Notes:

  • Take the runtime configuration into account for memcache - memcached has no such config, it should probably use container parameters.

Doc (for later...)

  • Refactor the doc
  • Document how to add / override backend & provider factories from any bundle
Clone this wiki locally