Hi all, I implemented the caching because I needed it for the handbook app to be usable, as I have explained before. You are right: No decision was made and it was obvious that no decision was going to be made for now as I seem to be the only one who needs caching short-term.
So I had some options: do nothing and not release the handbook application or release an application that is going to drive people crazy; just implement some caching mechanism in the handbook application, making it only usable there (while there is some caching on the session in the portfolio app I really want to get rid of too) OR implement it without everyone's blessing and just keep it out of the core by making it an optional app. The optional app obviously is work in progress but shouldn't bother anybody else since 1) you can implement different caching mechanisms there and use the one best suited for your needs or the one that best fits your religious believes or whatever 2) you can turn off caching completely by setting "no caching" as a standard and disallowing all other implemented mechanisms 3) it doesn't have to be installed anyway if you don't use the handbook application. I am currently documenting and doing some clean-up in the handbook application. Once this is finished I will do the same for the caching app (although it is pretty straight-forward I think). If I have time I will do another simple implementation for maybe file caching and/or apc to test which one is faster in the particular case of the handbook table of content. Off course this absolutely does not mean we cannot discuss this further. This does also not mean this is the way we should implement things in the long run. It is just a pragmatic, short-term solution to a very real problem. Kind regards, Nathalie Op 05/06/2011 02:33 PM, Sven Vanpoucke schreef: > Dear fellow developers > > As 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. >
_______________________________________________ Dev mailing list Dev@lists.chamilo.org http://lists.chamilo.org/listinfo/dev
