mirror of
https://github.com/Karaka-Management/Developer-Guide.git
synced 2026-01-11 12:28:41 +00:00
Init new chapters
This commit is contained in:
parent
df4935f892
commit
a5d554ca26
57
caching,_sessions,_local_storage_&_cookies.md
Normal file
57
caching,_sessions,_local_storage_&_cookies.md
Normal file
|
|
@ -0,0 +1,57 @@
|
|||
# Caching, Sessions, Local Storage & Cookies
|
||||
|
||||
## Caching
|
||||
|
||||
For caching the `CacheManager` provides access to the caching systems in place.
|
||||
Out of the box the CacheManager supports and automatically initializes either
|
||||
Redis or Memcached depending on the client configuration. The caching is
|
||||
not mandatory and therfor shouldn't be missuesed as in-memory database. It is
|
||||
not necessary to check if Redis or Memcached are available the CacheManager
|
||||
automatically handles the caching based on their existence.
|
||||
|
||||
### HTTP Cache
|
||||
|
||||
By default only stylesheets, javascript and layout images as well as module
|
||||
images are cached. Everything else is considered volatile and not cached.
|
||||
If a response specific response should be cached feel free to use the
|
||||
response header:
|
||||
|
||||
Example usage for 30 days caching:
|
||||
|
||||
```
|
||||
$resposne->setHeader('Cache-Control', 'Cache-Control: max-age=2592000');
|
||||
```
|
||||
|
||||
In order to trigger a re-cache of stylesheets or javascript files make sure to
|
||||
include their version hash as file name. This way version updates will result
|
||||
in a new file name and will be re-cached by the client browser.
|
||||
|
||||
Example usage:
|
||||
|
||||
```
|
||||
$head->addAsset(AssetType::JS, $request->getUri()->getBase() . 'Modules/Media/ModuleMedia_' . self::$version . '.js');
|
||||
```
|
||||
|
||||
## Sessions
|
||||
|
||||
Sessions are handled via the `SessionManager`. Sessions can be set and
|
||||
manipulated from the web application as well as the socket or console
|
||||
application.
|
||||
|
||||
### HTTP
|
||||
|
||||
The Http session will be saved automatically, there is no need to access the
|
||||
super global `$_SESSION`. Make sure to only modify session data using the
|
||||
SessionManager
|
||||
|
||||
### Socket & Console
|
||||
|
||||
The session will be stored and assoziated with the logged in user in memory.
|
||||
A disconnect or quit is considered as a logout and therefor results in the
|
||||
destruction of the session object of this user and will be empty for the
|
||||
next login.
|
||||
|
||||
## Local Storage
|
||||
|
||||
|
||||
## Cookies
|
||||
4
datamapper_&_query_builder.md
Normal file
4
datamapper_&_query_builder.md
Normal file
|
|
@ -0,0 +1,4 @@
|
|||
# DataMapper & Query Builder
|
||||
|
||||
|
||||
|
||||
21
modules.md
Normal file
21
modules.md
Normal file
|
|
@ -0,0 +1,21 @@
|
|||
# Modules
|
||||
|
||||
## Info
|
||||
|
||||
## Install
|
||||
|
||||
## Update
|
||||
|
||||
## Uninstall
|
||||
|
||||
## Routing
|
||||
|
||||
## Model, View, Controller, Template
|
||||
|
||||
## Resources
|
||||
|
||||
## Providing
|
||||
|
||||
## Requesting
|
||||
|
||||
## Receiving
|
||||
Loading…
Reference in New Issue
Block a user