Commit Graph

8 Commits

Author SHA1 Message Date
Ralf Becker
64f31a0fdc * Setup/API: translations are no longer installed in database, but loaded directly from lang-files into tree-level cache
also backported:
- r40748: loading all translations in one go from cachem, saving some latency
- r36329: config is now cached on instance level, arrays in $GLOBALS[egw_info][server] are now automatically serialized and unserialized
2012-11-15 19:12:15 +00:00
Ralf Becker
19e8654778 * Admin: new function "Clear cache and register hooks", also called automatic when restoring a backup 2012-11-05 14:10:23 +00:00
Ralf Becker
db729eac41 tests for egw_cache_provider and not using APC for cli, if apc.enable_cli is not set
Also did some benchmarking on my Macbook (with a SSD and memcached running on localhost):
Checking egw_cache_memcache:
0 checks failed, 100 iterations took 0.480 sec

Checking egw_cache_apc:
0 checks failed, 100 iterations took 0.025 sec

Checking egw_cache_files:
0 checks failed, 100 iterations took 0.826 sec
--> APC is by a factor of 20 faster then memcached, which is double as fast compared to files on a SSD
2012-04-13 10:22:38 +00:00
Klaus Leithoff
ddb2190927 fix typo 2011-11-02 14:59:27 +00:00
Andreas Stöckel
43e4fa2c3c Updated the thumbnail generator to use the egw_cache_file class to generate a temp filename 2011-02-21 18:37:45 +00:00
Ralf Becker
edea73521e "quitent some warnings about not writable dirs, eg. if calling cli programms with users not having permissions for the cache dir" 2009-05-02 12:33:28 +00:00
Ralf Becker
b6eda8e39b "replacing colons with dashes in filenames, as some windows installs seem to have problem with colons in filenames" 2009-04-29 16:08:13 +00:00
Ralf Becker
fd9856ebf5 Class to manage caching in eGroupware:
It allows to cache on 4 levels:
a) tree:     for all instances/domains runining on a certain source path
b) instance: for all sessions on a given instance
c) session:  for all requests of a session, same as egw_session::appsession()
d) request:  just for this request (same as using a static variable)

There's a get, a set and a unset method for each level: eg. getTree()
or setInstance(), as well as a variant allowing to specify the level as first
parameter: eg. unsetCache()

getXXX($app,$location,$callback=null,array $callback_params,$expiration=0)
has three optional parameters allowing to specify:
3. a callback if requested data is not yes stored. In that case the
   callback is called and it's value is stored in the cache AND retured
4. parameters to pass to the callback as array, see call_user_func_array
5. an expiration time in seconds to specify how long data should be cached,
   default 0 means infinit (this time is not garantied and not
   supported for all levels!)

Data is stored under an application name and a location, like
egw_session::appsession().
In fact data stored at cache level egw_cache::SESSION, is stored in
the same way as egw_session::appsession() so both methods can be used
with each other.

The $app parameter should be either the app or the class name, which
both are unique.

The tree and instance wide cache uses a certain provider class, to
store the data eg. in memcached or if there's nothing else configured
in the filesystem (eGW's temp_dir).
2009-04-20 11:50:45 +00:00