Cheers Sven, I am afraid you were faster than me. So far I added the following:
- client (browser caching)
- server resource caching (css/javascript) on disk
- system caching of configuration (global/user settings plus
registrations) on disk, i.e.
While I understand the overall caching issue is still very much in discussion those tackle different problems:
Broswer/Resource is all about js/css.
System caching is about speeding up global.
which have different requirements than setting up a global caching
policy. Typically file caching of css/js is going to stay whatever the
final solution. Browser caching is well, browser, specific. And system
caching requires an all or nothing approach. Not speaking about global
that was extremely sluggish.
Now I certainly agree that we should discuss our caching strategy but I would like to add a point. The question has less to do about caching itself, which has been around for quite some time, and more about how we are going to use it. That being said I am very much for further discussing our approach.
More to come about the changes. Le 06.05.2011 14:33, Sven Vanpoucke a écrit :
Dear fellow developersAs you all may know we have been discussing the topic of caching in chamilo a few weeks ago on the mailing list. As far as i know there was not a real decision about how it would be implemented and who would implement it. Though there was no real decision i have noticed that some of you already did some kind of implementation of caching (both as an optional app and in the core). I do not like the idea that it already has been implemented in the core since there was no real decision about the caching . I'd rather have some kind of proof of concept that it's really easy and good to use with the use of an optional application.I do realize that we are all on a very tight schedule and that we need to make sure we get finished in time but we should try to avoid implementing some quick solutions without proper analysis because of the deadlines. This will cause our platform to become as chaotic as the software we once came from...I propose that we try to discuss these matters and try to reach an agreement before implementing them (with proper analysis and planning of who will do what and when). If an agreement can not be found about these kind of topics then I propose that our software coordinator, Hans, takes the final decision.
-- ____________________________________ Meilleures salutations Laurent Opprecht chat: laurent.oppre...@gmail.com blog: http://ciel.unige.ch/
<<attachment: laurent_opprecht.vcf>>
_______________________________________________ Dev mailing list Dev@lists.chamilo.org http://lists.chamilo.org/listinfo/dev
