I have been doing a little bit of work on bibliocello (based on Pier2
and Seaside3.0) over the last week and one of things that I've found is
that one can avoid the per request commits (caused by saving Seaside
session state ... new session state is created even for "read only"
requests) by using a RESTful api like the one that Philippe has created
(Seaside-REST in the
http://www.squeaksource.com/Seaside30Addons
repository)..the neat thing about Philippe's api is that you can
intermix REST and stateful Seaside calls with relative ease...
Dale