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