Hi Laurent, as long as the caching "app" is only used by other optional applications it is not such a problem, since you can make it a prerequisite for the application so you can always be sure the classes exist.
If core-applications want to use the caching it will have to become a core application anyway and I agree that in the long run that is the most logical step. but for now I can have my caching without touching the core and everybody has time to review/adapt/improve things before they are moved to the core. if it becomes core i agree it would be nice to merge the admin tools. kind regards, Nathalie Op 05/03/2011 04:34 PM, Laurent Opprecht schreef: > Cheers Nathatlie, > Thanks for the work. > > While I understand the reasons to put it in a separate package I think > it would be better if we moved it to the core. If not now then at > least in the future. > There are several parts - global comes to my mind - that would very > much benefit from it. > If we don't put it in the core we will have to make plenty of test on > the line of: if class exist do that if not do this. > If we move it to the core we can set it up to return a empty cache. > I.e. one that does nothing and returns null. > > BTW I have started working on css/javascript caching - on the client > side that is. So it may be worth at some point to merge the admin tool. > > > Le 03.05.2011 15:42, Nathalie Blocry a écrit : >> Hi all, >> >> I have made an extra, optional, Chamilo 2 application to handel the >> caching for the handbook and portfolio for now. >> https://bitbucket.org/NathalieB/chamilo-app-cache-dev/ >> >> it is set-up so you can use different caching-mechanisms (applications >> can specify which caching implementation to use, or can just use the >> default caching mechanism) once they are implemented. >> >> for now I have only started a first implementation for caching to a >> database table. in the future we can add things like memcached and apc >> and filecaching if needed. >> >> this way, it is not in the core but still easily installable and usable >> by applications that need caching. >> >> I will make available a component where admins can clear the cache, so >> even users who can't use a cron-script can clean up things manually. >> since it is not a core-application I cannot do things like clearing the >> cache when a user logs out, but that wasn't considered to be a good idea >> anyway. >> >> obviously it is still work in progress. >> >> kind regards, >> Nathalie >> >> 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. >>> -- >>> ____________________________________ >>> 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 > > > -- > ____________________________________ > 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
