[Seaside] what objects can i register for backtracking?

[Cees de Groot]

On Thu, 2004-01-08 at 19:37, Avi Bryant wrote:
> [...] the simplest and most reliable solution is to have each 
> transaction/unit of work only exist for a single request. 
>
Talking about this - what's the current way of wrapping Seaside
processing in a transaction? Can it be done by Seaside hooks or do I
somehow need to make this explicit in my app?

(I'm almost ready to start putting OmniBase below Gardner...)