Op 04/26/2011 12:26 PM, Sven Vanpoucke schreef: > I don't think it's a good idea to use caching in the session variable. this is exactly why I am looking for the best alternative. caching on the session was done for now to test how much it would speed things up.
Op 04/26/2011 12:42 PM, Laurent Opprecht schreef: > 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. I think this might be a good idea, so you avoid exluding memcached *ONLY* because it would require something extra to be installed, while it *MIGHT* be the best solution (I don't know if it is) Op 04/26/2011 12:26 PM, Sven Vanpoucke schreef: > I think in your case, the best solution could be to have a DB table in > the content object of the handbook which stores the menu and which > gets updated whenever the handbook changes. the problem is that there is no *THE* menu, as every user will have his own context (language, institution, learning style, programme, ...) and the "best" version might differ. so at least I would need one db-entry per user (per session?)
_______________________________________________ Dev mailing list Dev@lists.chamilo.org http://lists.chamilo.org/listinfo/dev
