Ticket #16785: docs-misc-design-philosophies-cache.patch

File docs-misc-design-philosophies-cache.patch, 1.2 KB (added by jamesp, 3 years ago)
  • docs/misc/design-philosophies.txt

    diff --git a/docs/misc/design-philosophies.txt b/docs/misc/design-philosophies.txt
    index e6aea33..b06ca2e 100644
    a b Differentiate between GET and POST 
    310310
    311311GET and POST are distinct; developers should explicitly use one or the other.
    312312The framework should make it easy to distinguish between GET and POST data.
     313
     314Cache
     315=====
     316
     317The core goals of a cache are:
     318
     319Less code
     320---------
     321
     322A cache should be as fast as possible.  Hence, all framework code surrounding
     323the cache backend should be kept to the absolute minimum, especially for
     324``get()`` operations.
     325
     326Consistency
     327-----------
     328
     329The cache backend should implement an interface consistent across the
     330currently-supported cache backends.
     331
     332Extensibility
     333-------------
     334
     335The cache API should be extensible at the application level based on the
     336developer's needs (see :ref:`Cache Key Transformation
     337<cache_key_transformation>`).
     338
     339Explicit is better than implicit
     340--------------------------------
     341
     342In addition to incurring processing costs, magically resolving a potentially
     343invalid key in the framework may obscure issues with the cache backend, making
     344development more difficult.
Back to Top