http://community.postnuke.com/Article2894.htm PostNuke CMS Newsfeed en-gb http://community.postnuke.com/images/logo.gif http://community.postnuke.com/ pnwebmaster@postnuke.com http://community.postnuke.com/http://community.postnuke.com/Article2894.htm#comment26009 Tue, 04 Mar 2008 23:28:46 +0000 http://community.postnuke.com/http://community.postnuke.com/Article2894.htm#comment26009 good point, Chris. Dynamic pages, in several languages with several overlapping permission groups and the need to avoid concurrency problems... quite a task. Volunteers? ;-) http://community.postnuke.com/http://community.postnuke.com/Article2894.htm#comment26007 Tue, 04 Mar 2008 15:36:51 +0000 http://community.postnuke.com/http://community.postnuke.com/Article2894.htm#comment26007 While we work on the better multilingual features for 0.9 we should also take into account it's relation with our caching strategies. So, it's not just objects and queries, but also the new language system which must play well with caching. Greetings, Chris http://community.postnuke.com/http://community.postnuke.com/Article2894.htm#comment26005 Tue, 04 Mar 2008 11:33:52 +0000 http://community.postnuke.com/http://community.postnuke.com/Article2894.htm#comment26005 PostNuke supports/will support caching at all levels - whether very high (pages), granular (module/items) or low level (database queries/objects). Each level has its advantages and disadvantages, most of which have already been discussed at length. The challenge moving forward to .9/1.0 is to create a coherent caching strategy that can work at whatever level is suitable for an administrator's site. Right now, the caching is there, but not in an ideal state - and it's on the list to be more fully developed in the future. http://community.postnuke.com/http://community.postnuke.com/Article2894.htm#comment26002 Tue, 04 Mar 2008 09:22:15 +0000 http://community.postnuke.com/http://community.postnuke.com/Article2894.htm#comment26002 perhaps he just wants to cache the object and not the full page , in this case you don't have problems with permissions no ? http://community.postnuke.com/http://community.postnuke.com/Article2894.htm#comment26001 Tue, 04 Mar 2008 08:44:07 +0000 http://community.postnuke.com/http://community.postnuke.com/Article2894.htm#comment26001 Main problem in caching is our extended permission system which has to be taken into account when caching a page. This gets even where worse if you start to include another modules output in your templates, eg. showing a formicula form in a Pagesetter publication: You might have the permission to see the page, but you may not be allowed to use the contact form. Joomla does not have this granular system iirc so they don't have the problem at all. No go and choose your poison :-) http://community.postnuke.com/http://community.postnuke.com/Article2894.htm#comment26000 Mon, 03 Mar 2008 23:33:10 +0000 http://community.postnuke.com/http://community.postnuke.com/Article2894.htm#comment26000 excuse me, but why would you like to implement such a complex system with objects (and probably something we could call states like this [img]http://download-uk.oracle.com/docs/html/B25947_01/img/entitystates.gif[/img]) as you can only use something like the AdoDB Cache system,directly on the most used queries of the CMS (the queries that are called on each page and who load mostly configuration variables), which is perhaps a simplier way to handle this. [url=http://www.phpeveryday.com/articles/ADOdb+Caching+of+Recordset-P22.html]sample use[/url] http://community.postnuke.com/http://community.postnuke.com/Article2894.htm#comment25999 Mon, 03 Mar 2008 19:20:14 +0000 http://community.postnuke.com/http://community.postnuke.com/Article2894.htm#comment25999 More thoughts on caching - perhaps just a cache trigger in api calls - if the cache trigger is true, pnobj calls invalidate the cache of the obj and any objarray caches that obj is in. http://community.postnuke.com/http://community.postnuke.com/Article2894.htm#comment25998 Mon, 03 Mar 2008 19:18:52 +0000 http://community.postnuke.com/http://community.postnuke.com/Article2894.htm#comment25998 Thanks for the info. Two cents: Caching should be done on the object level - ie, when an object changes significantly, it's cached again. Until another db change, the cache is used. Perhaps a pnObj cache mechanism. The difficulty comes in knowing which DB updates are necessary for a cache refresh - a counter increment should not, a title change should - and how to notify any objArray caches that a member of its cache is now updated. Doesn't joomla use an object cache? Anyone poked into their implementation of it? NCM http://community.postnuke.com/http://community.postnuke.com/Article2894.htm#comment25997 Mon, 03 Mar 2008 14:17:33 +0000 http://community.postnuke.com/http://community.postnuke.com/Article2894.htm#comment25997 I saw I also forgot to mention the people responsible for each subject (for the proper credits ;-) )... will do so next time. [quote]There is one information missing that might be important as well: We plan to release .8 as $newname 1.0.[/quote]Guess I missed that ;) http://community.postnuke.com/http://community.postnuke.com/Article2894.htm#comment25995 Mon, 03 Mar 2008 12:52:55 +0000 http://community.postnuke.com/http://community.postnuke.com/Article2894.htm#comment25995 Teb, thanks for working on the development updates again! There is one information missing that might be important as well: We plan to release .8 as $newname 1.0.