Return-Path: 
 <dev-return-44952-apmail-cocoon-dev-archive=cocoon.apache.org@cocoon.apache.org>
Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org
Received: (qmail 96080 invoked by uid 500); 15 Jul 2003 16:33:16 -0000
Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:dev-help@cocoon.apache.org>
list-unsubscribe: <mailto:dev-unsubscribe@cocoon.apache.org>
list-post: <mailto:dev@cocoon.apache.org>
Reply-To: dev@cocoon.apache.org
Delivered-To: mailing list dev@cocoon.apache.org
Received: (qmail 96062 invoked from network); 15 Jul 2003 16:33:15 -0000
Received: from out006pub.verizon.net (HELO out006.verizon.net)
 (206.46.170.106)
  by daedalus.apache.org with SMTP; 15 Jul 2003 16:33:15 -0000
Received: from verizon.net ([4.40.118.187]) by out006.verizon.net
          (InterMail vM.5.01.05.33 201-253-122-126-133-20030313) with ESMTP
          id <20030715163318.EZFC16647.out006.verizon.net@verizon.net>
          for <dev@cocoon.apache.org>; Tue, 15 Jul 2003 11:33:18 -0500
Message-ID: <3F142CCC.2010008@verizon.net>
Date: Tue, 15 Jul 2003 09:33:16 -0700
From: Christopher Oliver <res1cf5x@verizon.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:1.0.2) Gecko/20030208 Netscape/7.02
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: [flow] session creation
References: <9C88FAE0-B622-11D7-845D-000393D2CB02@apache.org>
 <20030714194318.3264573612@smtp.us2.messagingengine.com>
 <3F131F93.6040904@leverageweb.com> <3F138D63.8090701@verizon.net>
 <3F13FF56.1060206@verizon.net> <3F1420CB.6090908@verizon.net>
 <3F142531.8090706@verizon.net> <3F142917.1030901@verizon.net>
 <3F142B99.4080701@leverageweb.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Authentication-Info: Submitted using SMTP AUTH at out006.verizon.net from
 [4.40.118.187] at Tue, 15 Jul 2003 11:33:18 -0500
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

Geoff Howard wrote:

> Christopher Oliver wrote:
>
>> Vadim Gritsenko wrote:
>
<snip>

>
>>> Geoff suggested couple of places:
>>>
>>>> This seems to be a good solution too, as long as it's not once per 
>>>> application.  It seems it would need to be on <map:flow> or 
>>>> <map:call>? 
>>>
>>>
>>> I think map:flow is appropriate.
>>
>>
>> +0 to turning on/off session creation in <map:flow>.
>>
>> -1 to having "request" or "context" scope.
>
>
> Again, this would seem fine to me.  I'm not sure I totally understand 
> the problem with context scope (though request I think I understand). 
> What potential for abuse or error do you see?
>
> Geoff
>
If you allow modification of global variables, then multiple users would 
be able to modify the same variables.  If not, then you don't need any 
dynamic storage at all.

Chris