Hey Kay,
have a look at this module
http://www.syseleven.de/blog/1934/oxid-super-cache-mehr-power-fur-den-shop/
Developed by Fatchip and syseleven... interesting..
Best regards
Thomas Neumann
smart ecom - eCommerce Consulting
Gustav-Linden-Strasse 23
40878 Ratingen
m 0151 / 419 043 13
e
Hi Thomas,
yes, I know about that, but this is - again - the same thing with
sessions. HTML is stored - not in local directory, but on a
memcached-service - but we have the same result. As soon as there is a
session (user-data somewhere in the full html-document) the cache is
useless and we wont
Hi,
We developed a site caching module that allows you to configure
which pages will be cached, depending on what kind of
user depending information you show on the pages you could cache a
lot more than using this method. Send me an e-mail
for more information
Hello,
I think the Problem in building good caching-extensions is that we have no
low-level extension possibilities.
If we were able to extend base classes we could overload oxbase::load,
oxlist::selectString or even better oxDb::getDb, and could add in intelligent
caching code.
So i think
Hi Holger,
this is exactly what I think, but as we can see in several former
discussions: this will not be implemented in the near future. I would
even go further and try to avoid any session-data but the id. I think we
come to the question of sticking to the oxid-framework or switching to
Hi,
as far as I known there is also the possibility to cache parts of a site.
Es grüßen die Bergfreunde,
Till
P.S.: Neues gibt's im Blog sowie bei Facebook Twitter!
Bergfreunde GmbH
Till Voß
Leiter Online-Technik
Bahnhofstraße 26
72138 Kirchentellinsfurt
Telefon: +49 (0)7121 30459-24
Fax:
Hi Till,
what do you mean? In wich Version of Oxid and with what kind of technique?
Kai
Am 21.10.2011 16:26, schrieb Online-Technik - Bergfreunde.de:
Hi,
as far as I known there is also the possibility to cache parts of a site.
Es grüßen die Bergfreunde,
Till
P.S.: Neues gibt's im
Hi Kai,
I referred to the E-Mail I answered:
Hi Thomas,
yes, I know about that, but this is - again - the same thing with sessions.
HTML is stored - not in local directory, but on a memcached-service - but
we have the same result. As soon as there is a session (user-data somewhere
in