cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefano Mazzocchi <>
Subject Re: SoC between flow and sitemap
Date Tue, 20 May 2003 16:45:09 GMT
on 5/20/03 3:55 AM Giacomo Pati wrote:

> On Mon, 19 May 2003, Stefano Mazzocchi wrote:
>>on 5/18/03 4:53 PM Sylvain Wallez wrote:
> <sip/>
>>>Now we could adapt the continuation naming schemes. Currently, we have a
>>>single global naming space with long numbers to ensure uniqueness and
>>>avoid "continuation hijacking". We could have a simpler naming scheme
>>>for those continuations where the global variable scope is tied to the
>>>session (using Cocoon.createSession). This could even be a simple
>>>integer sequence, with an initial prefix to differentiate them from
>>>global continuations. This would also solve potential problems of the
>>>ContinuationsManager on clustered servers.
> <snip/>
>>So, what do you think if we dropped sessions-less continuations
>>alltogether and have the flow engine transparently create a session for
>>you in all cases?
> It might create unnecessary session objects. We have an flow app where the main
> entry point first checks the user supplied by the authentication mechs to see if
> that user has the authorisation to use the app and only at that point the
> session will be created.

What about calling removeSession() in that case?


View raw message