Comments on: OSCON 2006: Web Heresies: The Seaside Framework http://www.sitepoint.com/blogs/2006/07/28/oscon-2006-web-heresies-the-seaside-framework/ Tue, 07 Oct 2008 23:18:48 +0000 http://wordpress.org/?v=2.5 By: mde http://www.sitepoint.com/blogs/2006/07/28/oscon-2006-web-heresies-the-seaside-framework/#comment-41741 mde Tue, 01 Aug 2006 05:30:50 +0000 http://www.sitepoint.com/blogs/?p=1655#comment-41741 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'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. 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’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.

]]> By: Kevin Yank http://www.sitepoint.com/blogs/2006/07/28/oscon-2006-web-heresies-the-seaside-framework/#comment-41034 Kevin Yank Fri, 28 Jul 2006 14:14:26 +0000 http://www.sitepoint.com/blogs/?p=1655#comment-41034 didimo, I'm afraid you missed the point. Even storing sessions in a memory table requires you to serialize the session data. You can't store the current execution context, including the call stack, in a database. didimo,

I’m afraid you missed the point. Even storing sessions in a memory table requires you to serialize the session data. You can’t store the current execution context, including the call stack, in a database.

]]> By: didimo http://www.sitepoint.com/blogs/2006/07/28/oscon-2006-web-heresies-the-seaside-framework/#comment-40979 didimo Fri, 28 Jul 2006 08:47:08 +0000 http://www.sitepoint.com/blogs/?p=1655#comment-40979 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 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

]]>