<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: OSCON 2006: Web Heresies: The Seaside Framework</title>
	<atom:link href="http://www.sitepoint.com/blogs/2006/07/28/oscon-2006-web-heresies-the-seaside-framework/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.sitepoint.com/blogs/2006/07/28/oscon-2006-web-heresies-the-seaside-framework/</link>
	<description>News, opinion, and fresh thinking for web developers and designers. The official podcast of sitepoint.com.</description>
	<lastBuildDate>Sun, 08 Nov 2009 20:06:11 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: mde</title>
		<link>http://www.sitepoint.com/blogs/2006/07/28/oscon-2006-web-heresies-the-seaside-framework/comment-page-1/#comment-41741</link>
		<dc:creator>mde</dc:creator>
		<pubDate>Tue, 01 Aug 2006 05:30:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=1655#comment-41741</guid>
		<description>I was in the Seaside session too, and it was kind of astonishing to see what you can do when you set aside a lot of the traditional approaches to developing a Web app. 

On the other hand, the idea of using programming code to generate your markup isn&#039;t all that heretical to client-side developers who do it all the time with JavaScript. :) We just do it right there on the client instead of going back to the Web server for it.</description>
		<content:encoded><![CDATA[<p>I was in the Seaside session too, and it was kind of astonishing to see what you can do when you set aside a lot of the traditional approaches to developing a Web app. </p>
<p>On the other hand, the idea of using programming code to generate your markup isn&#8217;t all that heretical to client-side developers who do it all the time with JavaScript. :) We just do it right there on the client instead of going back to the Web server for it.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin Yank</title>
		<link>http://www.sitepoint.com/blogs/2006/07/28/oscon-2006-web-heresies-the-seaside-framework/comment-page-1/#comment-41034</link>
		<dc:creator>Kevin Yank</dc:creator>
		<pubDate>Fri, 28 Jul 2006 14:14:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=1655#comment-41034</guid>
		<description>didimo,

I&#039;m afraid you missed the point. Even storing sessions in a memory table requires you to serialize the session data. You can&#039;t store the current execution context, including the call stack, in a database.</description>
		<content:encoded><![CDATA[<p>didimo,</p>
<p>I&#8217;m afraid you missed the point. Even storing sessions in a memory table requires you to serialize the session data. You can&#8217;t store the current execution context, including the call stack, in a database.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: didimo</title>
		<link>http://www.sitepoint.com/blogs/2006/07/28/oscon-2006-web-heresies-the-seaside-framework/comment-page-1/#comment-40979</link>
		<dc:creator>didimo</dc:creator>
		<pubDate>Fri, 28 Jul 2006 08:47:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=1655#comment-40979</guid>
		<description>Heh my own framework uses database to store temporary and permament session, allowing me to store large objects in a session, the nice thing is that this scales quite well my latest project involves hundreds to thousands of users being online simultaneously

I found Memory tables perfect for this task, also innodb is surprisingly fast (im using mysql5,php5.1.4,apache2.2</description>
		<content:encoded><![CDATA[<p>Heh my own framework uses database to store temporary and permament session, allowing me to store large objects in a session, the nice thing is that this scales quite well my latest project involves hundreds to thousands of users being online simultaneously</p>
<p>I found Memory tables perfect for this task, also innodb is surprisingly fast (im using mysql5,php5.1.4,apache2.2</p>]]></content:encoded>
	</item>
</channel>
</rss>
