> 
> Which brings us back to the original question:  what's the best way to
> manage those sessions?  Frankly, I'm a little unsure of the "correct"
> mapping between Magma sessions and running Processes.  I'm also
> unclear regarding how Magma manages session consistency (I get the
> feeling that Auto sessions automatically refresh themselves at the
> start of a commit:, but I'm not entirely sure about that).
> 
The Seaside sessions or the MagmaSessions? Anyway:

	For Seaside sessions you don’t manage them, Seaside does it for you.
It's just about a few *concurrent* seaside sessions per image will make the
image to work more reliably (memory stable and such). In case you need more than
a few users concurrently, you use N images with the same application balanced
with an apache.

	For MagmaSessions you should use a session pool as I already said to you

	cheers,

Sebastian