Re: I-D ACTION:draft-daboo-sieve-include-03.txt (fwd)

Alexey Melnikov <alexey.melnikov@isode.com> Mon, 05 September 2005 09:19 UTC

Received: from above.proper.com (localhost.vpnc.org [127.0.0.1]) by above.proper.com (8.12.11/8.12.9) with ESMTP id j859JLDR078111; Mon, 5 Sep 2005 02:19:21 -0700 (PDT) (envelope-from owner-ietf-mta-filters@mail.imc.org)
Received: (from majordom@localhost) by above.proper.com (8.12.11/8.12.9/Submit) id j859JLuj078110; Mon, 5 Sep 2005 02:19:21 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-mta-filters@mail.imc.org using -f
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by above.proper.com (8.12.11/8.12.9) with ESMTP id j859JJIY078100 for <ietf-mta-filters@imc.org>; Mon, 5 Sep 2005 02:19:20 -0700 (PDT) (envelope-from alexey.melnikov@isode.com)
Received: from [192.168.0.2] ([62.3.217.253]) by rufus.isode.com via TCP (internal) with ESMTPA; Mon, 5 Sep 2005 10:19:13 +0100
Message-ID: <431B6F11.7070301@isode.com>
Date: Sun, 04 Sep 2005 23:02:57 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Aaron Stone <aaron@serendipity.cx>
CC: Sieve Mailing List <ietf-mta-filters@imc.org>
Subject: Re: I-D ACTION:draft-daboo-sieve-include-03.txt (fwd)
References: <twig.1125014327.8763@serendipity.palo-alto.ca.us> , <twig.1125014327.8763@serendipity.palo-alto.ca.us> <twig.1125020754.94965@serendipity.palo-alto.ca.us> <1125054534.15136.180.camel@chico.njus.no> <005c01c5aa44$49f18430$cf0ac050@nigelhome> <1125069059.15136.206.camel@chico.njus.no>, <1125069059.15136.206.camel@chico.njus.no> <twig.1125083963.7536@serendipity.palo-alto.ca.us> <028101c5ac9a$342ccee0$dbfac350@nigelhome> <4314936A.2060903@isode.com> <twig.1125435810.82298@serendipity.palo-alto.ca.us>
In-Reply-To: <twig.1125435810.82298@serendipity.palo-alto.ca.us>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-mta-filters@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-mta-filters/mail-archive/>
List-ID: <ietf-mta-filters.imc.org>
List-Unsubscribe: <mailto:ietf-mta-filters-request@imc.org?body=unsubscribe>

Aaron Stone wrote:

>On Tue, Aug 30, 2005, ""Nigel Swinson"" <Nigel.Swinson@rockliffe.com>
>said:  
>
>>>I think we all agree what the term "global variable" means in the 
>>>variables draft.
>>>But if people feel that the term "global variable" might be confusing, we 
>>>can still replace it with something else as an editorial change.
>>>      
>>>
>>Well at the risk of getting hit, I think it would be wise to change it from:
>>
>>   All variables have global scope: they are visible until processing
>>   stops.
>>
>>To:
>>
>>   All variables have file scope: they are visible to the remainder
>>   of the current script. 
>>
>
>As Kjetil pointed out last week, there is only one script, though there
>may be many files included. We should be careful not to confuzzle the two
>words.
>
And considering that the term "file" is not currently used in the 
variables draft, I would rather not introduce a new term just to define 
"scope".

>Also, from the point of view of the variables draft in a vacuum,
>there is only one file, only one script, and only one scope. 
>  
>
Right.

>How about this:
>
>    All variables have global scope within a script. Future specifications
>    may allow for a script to be composed of more than one file,
>
How about replacing "file" with more abstract "part"?
Sieve scripts are not necessarily stored as files.

>    or for
>    running more than one script per message [delivery?].
>
"per delivery" or "per message per recipient" is better, IMHO.
One message can have multiple recipients, all subject to different Sieve 
filters.

> Such
>    specifications may provide for different variable scoping rules.
>  
>