Support for alternative bytecode caches

Discussions and requests related to new CMSimple features, plugins, templates etc. and how to develop.
Please don't ask for support at this forums!
Post Reply
cmb
Posts: 14225
Joined: Tue Jun 21, 2011 11:04 am
Location: Bingen, RLP, DE
Contact:

Support for alternative bytecode caches

Post by cmb » Tue Aug 04, 2015 7:21 pm

Hi everybody!

As of CMSimple_XH 1.6 we cater to Zend OPcache when storing config and language files from the back-end by explicitly invalidating the file afterwards. There are several alternative byte code caches around, at least some of them are probably dead. However, just today a Danish user reported problems which are likely related to XCache. There is also WinCache which is actively maintained. We may consider to cater to these two (and maybe others) also.

Anyhow, I suggest that we offer this functionality (i.e. invalidating a single file, if possible, otherwise invalidate the complete cache) as API to be usable from plugins; at least some plugins store data as PHP files, what is likely to result in malfunctions if heavy caching is configured.

With regard to XCache: it is not possible to invalidate individual files yet, so we'd probably have to call xcache_clear_cache().
Christoph M. Becker – Plugins for CMSimple_XH

Post Reply