<?xml version="1.0" encoding="utf-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dc = "http://purl.org/dc/elements/1.1/" xmlns="http://purl.org/rss/1.0/">
	<channel rdf:about="http://livedocs.adobe.com/">
	<title>LiveDocs Comments - wtg - public - machiidevguide - views.html</title>	
		<link>http://livedocs.adobe.com/</link>
		<description>Macromedia LiveDocs - online documentation with user feedback.</description>
		<copyright>Copyright 2009, Macromedia, Inc.</copyright>
		<dc:date>2009-11-25T01:12:16</dc:date>
		<dc:language>en-us</dc:language>
		<items>
			<rdf:Seq>
				<rdf:li rdf:resource="http://livedocs.adobe.com/wtg/public/machiidevguide/views.html#17394" />
				<rdf:li rdf:resource="http://livedocs.adobe.com/wtg/public/machiidevguide/views.html#16999" />
				<rdf:li rdf:resource="http://livedocs.adobe.com/wtg/public/machiidevguide/views.html#9842" />
				<rdf:li rdf:resource="http://livedocs.adobe.com/wtg/public/machiidevguide/views.html#8626" />
				<rdf:li rdf:resource="http://livedocs.adobe.com/wtg/public/machiidevguide/views.html#4263" />
				<rdf:li rdf:resource="http://livedocs.adobe.com/wtg/public/machiidevguide/views.html#4261" />
				<rdf:li rdf:resource="http://livedocs.adobe.com/wtg/public/machiidevguide/views.html#4160" />
				<rdf:li rdf:resource="http://livedocs.adobe.com/wtg/public/machiidevguide/views.html#3830" />
			</rdf:Seq>
		</items>
	</channel>
	
	<item rdf:about="http://livedocs.adobe.com/wtg/public/machiidevguide/views.html#17394">
		<title>wtg/public/machiidevguide/views.html</title>
		<link>http://livedocs.adobe.com/wtg/public/machiidevguide/views.html#17394</link>
		<description>That is pretty much what we do with cf_accelerate on macromedia.com except we use a filter instead of a plugin (so I think your approach is just fine).</description>
		<dc:creator>SeanCorfield</dc:creator>
		<dc:type>1 0</dc:type>
		<dc:date>2004-06-21T16:55:48</dc:date>
	</item>
	<item rdf:about="http://livedocs.adobe.com/wtg/public/machiidevguide/views.html#16999">
		<title>wtg/public/machiidevguide/views.html</title>
		<link>http://livedocs.adobe.com/wtg/public/machiidevguide/views.html#16999</link>
		<description>about cache.&lt;br /&gt;as caching is important in buseness apps such as those machii is indicated to develop with, we revert the order of events handling, i.e. when a page including any dinamic contents is requested, an event to displaying it is generated: a plugin in this event handler can verify if the page is cached: if yes, the handler continues display the page, if not, plugin stops current event handling and announce another event corrisponding to the sequence of operations to reconstruct the page.&lt;br /&gt;the layout page containing dinamic contents, the pods, can be designed as a portlet or pagelet, so we can manage pods caching in this page, without involving the framework.&lt;br /&gt;what ado you think about?</description>
		<dc:creator></dc:creator>
		<dc:type>0 0</dc:type>
		<dc:date>2004-06-16T07:29:23</dc:date>
	</item>
	<item rdf:about="http://livedocs.adobe.com/wtg/public/machiidevguide/views.html#9842">
		<title>wtg/public/machiidevguide/views.html</title>
		<link>http://livedocs.adobe.com/wtg/public/machiidevguide/views.html#9842</link>
		<description>While there is probably some performance hit in doing this, we have found performance to be perfectly acceptable, even under heavy load.</description>
		<dc:creator>SeanCorfield</dc:creator>
		<dc:type>1 0</dc:type>
		<dc:date>2004-03-05T11:23:25</dc:date>
	</item>
	<item rdf:about="http://livedocs.adobe.com/wtg/public/machiidevguide/views.html#8626">
		<title>wtg/public/machiidevguide/views.html</title>
		<link>http://livedocs.adobe.com/wtg/public/machiidevguide/views.html#8626</link>
		<description>How does the copying of large HTML fragments to the request scope on a continuous basis affect memory management and performance on high traffic sites?</description>
		<dc:creator>schipperheyn</dc:creator>
		<dc:type>0 0</dc:type>
		<dc:date>2004-02-22T05:54:36</dc:date>
	</item>
	<item rdf:about="http://livedocs.adobe.com/wtg/public/machiidevguide/views.html#4263">
		<title>wtg/public/machiidevguide/views.html</title>
		<link>http://livedocs.adobe.com/wtg/public/machiidevguide/views.html#4263</link>
		<description>There is no support within the framework for caching a single view (as &lt;br /&gt;the comment above indicates, you can cache an entire page).&lt;br /&gt;&lt;br /&gt;You could probably write your own view cache management using a &lt;br /&gt;filter, depending on how complex your view structure is.&lt;br /&gt;&lt;br /&gt;Remember: don't optimize unless you already proved you have a &lt;br /&gt;problem using load testing!</description>
		<dc:creator>SeanCorfield</dc:creator>
		<dc:type>0 0</dc:type>
		<dc:date>2003-12-01T12:06:19</dc:date>
	</item>
	<item rdf:about="http://livedocs.adobe.com/wtg/public/machiidevguide/views.html#4261">
		<title>wtg/public/machiidevguide/views.html</title>
		<link>http://livedocs.adobe.com/wtg/public/machiidevguide/views.html#4261</link>
		<description>What is the best method to cache queries stored as request.variable name for display in the views? &lt;br /&gt;&lt;br /&gt;&lt;cffunction name=&quot;getPressRelease&quot; returntype=&quot;query&quot;&gt;&lt;br /&gt;		&lt;cfquery name=&quot;qryPressRelease&quot; datasource=&quot;#request.dsn#&quot; cachedwithin=&quot;#CreateTimeSpan(0,24,0,0)#&quot; blockfactor=&quot;2&quot;&gt;&lt;br /&gt;			EXEC spPR&lt;br /&gt;		&lt;/cfquery&gt;&lt;br /&gt;		&lt;cfreturn qryPressRelease /&gt;&lt;br /&gt;	&lt;/cffunction&gt;&lt;br /&gt;&lt;br /&gt;However, &lt;notify listener=&quot;PressReleaseManager&quot; method=&quot;getPressRelease&quot; resultKey=&quot;request.PRs&quot; /&gt;&lt;br /&gt;			&lt;view-page name=&quot;pressRelease&quot; contentKey=&quot;request.pressRelease&quot; /&gt;&lt;br /&gt;&lt;br /&gt;The variable request.pressRelease is re-created... unlike the query which is cached... How can I cache request.pressRelease just like the query?</description>
		<dc:creator></dc:creator>
		<dc:type>0 0</dc:type>
		<dc:date>2003-12-01T11:58:21</dc:date>
	</item>
	<item rdf:about="http://livedocs.adobe.com/wtg/public/machiidevguide/views.html#4160">
		<title>wtg/public/machiidevguide/views.html</title>
		<link>http://livedocs.adobe.com/wtg/public/machiidevguide/views.html#4160</link>
		<description>You can cache full page views using a variety of content caching &lt;br /&gt;techniques. We're currently looking at Brandon Purcell's cf_accelerate &lt;br /&gt;tag as one option - and using a filter to abort the current event if the &lt;br /&gt;result is already in cache. It's not quite as straightforward to cache &lt;br /&gt;just a single pod because the framework doesn't currently allow for a &lt;br /&gt;plugin to abort a view-page directive (so you can't avoid rendering the &lt;br /&gt;view even if you have it cached).</description>
		<dc:creator>SeanCorfield</dc:creator>
		<dc:type>0 0</dc:type>
		<dc:date>2003-11-25T12:22:06</dc:date>
	</item>
	<item rdf:about="http://livedocs.adobe.com/wtg/public/machiidevguide/views.html#3830">
		<title>wtg/public/machiidevguide/views.html</title>
		<link>http://livedocs.adobe.com/wtg/public/machiidevguide/views.html#3830</link>
		<description>How do we have to manage caching of the view or pods ? &lt;br /&gt;By the use of filters ? is there some specific methodology to use ?</description>
		<dc:creator>lanfeustdetroy</dc:creator>
		<dc:type>0 0</dc:type>
		<dc:date>2003-11-14T05:58:16</dc:date>
	</item>
	</rdf:RDF>

