I hope that by now it's clear that this is a big subject, not to be
taken lightly at all. Implementing this before the freeze / merge /
whatever-you-want-to-call-it at the end of May does not seem realistic
to me. If and when this is implemented we need detailed "research" on
how this will happen, impact on the code base, detailed information on
how the different caching mechanisms would work, etc. Being able to keep
everything working on shared hosting space is paramount. It's ok if that
means sacrificing some speed, but it should work. This is also not the
kind of thing that can be implemented "a bit" either. It's either there
and usable everywhere or not there at all.
Looking forward to reading more on the subject via the wiki / mailing list.
On 27/04/2011 12:56, Philippe Van Eerdenbrugghe wrote:
If you go for cron, don't forget that chamilo should be usable on
mutalised hosting where cron is not available. What about file
serialization and var_export /__set_state() functions ?
the mtime can be checked directly in php code
Systho
Le 27/04/2011 12:46, Laurent Opprecht a écrit :
I believe a DB implementation would be a good first move - at least
we are sure it will be available :-).
I would just ensure the implementation is compatible in term of
interface with APC - which should be more or less a standard by now.
I.e. have functions such as add($key, $value, $time_to_leave) etc
I don't think we should clear the cache by logout. After all some
caching may still be usefull after logout. Cron would be my favorite.
Le 27.04.2011 11:29, Nathalie Blocry a écrit :
I have made a wiki page on this subject:
http://support.chamilo.org/projects/chamilo-20/wiki/Caching
I know striclty speaking this is a new feature but I am convinced we
really need some kind or caching before we can release the handbook app.
I could implement it for now just for the handbook, but if I am making
the effort anyway I think it would be better to implement the
platform-wide classes right-away, no?
So I propose making the Cache class and just doing one implementation
for now.
Still not sure what this one implementation should be.
nobody has any experience with caching data/objects (not pages)?
short-term serializing and storing in the database might be the best
default system? With some cron-script to periodically clean out the
table, because we can clean-up at logout, but not many users will
actualy do that I think (I never do ;-))
Op 04/26/2011 01:32 PM, Hans De Bisschop schreef:
That's the Chamilo 2.0 spirit *thumbs up* 8-) :-)
Hans
On 26/04/2011 12:42, Laurent Opprecht wrote:
We may abstract the caching mecanism.
Something like:
class Cache
class ApcCache extends Cache
class MemCache extends Cache
class DatabaseCache extends Cache
class SessionCache extends Cache
class EmptyCache extends Cache //Empty pattern
...
With a factory method inside the Cache class. If the cache is not
available - because memcach is not installed for example - then
we can return the Empty cache that does nothing or defaults to
anoter implementation.
That would make Chamilo independant from specific cache implemenation
yet providing the service for those applications that need it.
Le 26.04.2011 12:26, Sven Vanpoucke a écrit :
I would not use memcached or another tool for caching because this
would mean that we would demand yet another package to be installed
on the server before chamilo can be used.
--
____________________________________
Meilleures salutations
Laurent Opprecht
chat:laurent.oppre...@gmail.com
blog:http://ciel.unige.ch/
_______________________________________________
Dev mailing list
Dev@lists.chamilo.org
http://lists.chamilo.org/listinfo/dev
--
*Hans De Bisschop*
Hoofddeskundige ICTO | Lead Developer Chamilo 2.0
Software Coordinator Chamilo Association
Erasmushogeschool Brussel
Nijverheidskaai 170 | B-1070 Brussel
T 02 559 02 54 | i 254
hans.de.bissc...@ehb.be <mailto:hans.de.bissc...@ehb.be> |
www.erasmushogeschool.be <http://www.erasmushogeschool.be/>
Kom eens langs:www.erasmushogeschool.be/infodagen
<http://www.erasmushogeschool.be/infodagen>
of lees onze elektronische nieuwsbrief: ehbrief.ehb.be
<http://ehbrief.ehb.be/>
P Before printing, think about the environment
_______________________________________________
Dev mailing list
Dev@lists.chamilo.org
http://lists.chamilo.org/listinfo/dev
_______________________________________________
Dev mailing list
Dev@lists.chamilo.org
http://lists.chamilo.org/listinfo/dev
--
____________________________________
Meilleures salutations
Laurent Opprecht
chat: laurent.oppre...@gmail.com
blog: http://ciel.unige.ch/
_______________________________________________
Dev mailing list
Dev@lists.chamilo.org
http://lists.chamilo.org/listinfo/dev
_______________________________________________
Dev mailing list
Dev@lists.chamilo.org
http://lists.chamilo.org/listinfo/dev
--
*Hans De Bisschop*
Hoofddeskundige ICTO | Lead Developer Chamilo 2.0
Software Coordinator Chamilo Association
Erasmushogeschool Brussel
Nijverheidskaai 170 | B-1070 Brussel
T 02 559 02 54 | i 254
hans.de.bissc...@ehb.be <mailto:hans.de.bissc...@ehb.be> |
www.erasmushogeschool.be <http://www.erasmushogeschool.be/>
Kom eens langs: www.erasmushogeschool.be/infodagen
<http://www.erasmushogeschool.be/infodagen>
of lees onze elektronische nieuwsbrief: ehbrief.ehb.be
<http://ehbrief.ehb.be/>
P Before printing, think about the environment
_______________________________________________
Dev mailing list
Dev@lists.chamilo.org
http://lists.chamilo.org/listinfo/dev
