Web Frameworks (was Re: Squeak book !)

Cees de Groot cg at cdegroot.com
Tue Sep 3 19:04:56 UTC 2002


Avi Bryant <avi at beta4.com> said:
>Yes... this was the idea behind Seaside 2.0 - to have a series of layers,
>each of which could be the foundation for alternate approaches.  The
>continuation based session management I consider core, but Goran could
>layer an alternate form builder on top of it, or could use my callback
>based form builder but layer an alternate component system on top of it,
>etc.  Meanwhile, I'm thinking about various templating systems and
>MVC-like systems to layer on top of my components...
>
Do you have some call-outs for transaction management in there as
well? I've done some thinking (ouch - that hurts! Luckily, I'm a
manager nowadays so I can usually get by without it), and I guess that
whoever flamed me on the Seaside list for wanting to have long-running
transactions is probably right - one database transaction per web hit
is the way to go, the 'application transaction' must be dealt with on
the app level. So I think what's needed is to have some way of getting
notification so that Seaside tells me "I'm about to process a hit in
session X" and "answer written for this hit in session X". In fact, with
a list of dependents you could build quite some flexible logging classes
and profiling classes (I like to know when a hit costs more than, say, a 
second to process) that surf on the same mechanism. 

-- 
Cees de Groot               http://www.cdegroot.com     <cg at cdegroot.com>
GnuPG 1024D/E0989E8B 0016 F679 F38D 5946 4ECD  1986 F303 937F E098 9E8B
Cogito ergo evigilo



More information about the Squeak-dev mailing list