On Monday, Jul 14, 2003, at 11:20 America/Guayaquil, Geoff Howard wrote:


Christopher Oliver wrote:
Yes. That is a feature of the new FOM: it always creates a session. The original API had createSession() and removeSession(). Those functions were removed from FOM.

I thought that was only supposed to happen after a reference to cocoon.session, or when a continuation is created. Can someone confirm?



I think we didn't reach consensus on that, there were still different positions on the table.


I personally think that sessions should always be available from the flow, because I never felt the need to use flow without keeping some form of state but you seem to imply that your experience is different.

Can you show us how?

--
Stefano



Reply via email to