On 3 Sep 2002, Cees de Groot wrote:

> 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.

Yes, that would be nice.  It's easy to subclass the Session class and
override the request handling methods; you could place whatever hooks you
wanted and call the super method.  IASession>>viewPage: might be a good
method to look at in 0.9x, or WASession>>handleRequest:response: in
Borges.