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