Hi there,

i'd call it a process. Since you put in something on the top and get  
something out of the buttom.
If you add unit, you'll have a "processing unit" just like a CPU, but  
just a PU :)


Am 19.03.2009 um 14:13 schrieb David Zülke:

> That is bad, because it could also refer to the framework's internal  
> "engine" to execute something.
>
>
> On 19.03.2009, at 14:41, Felix Gilcher wrote:
>
>> Hi all,
>>
>> it's me again. Just to sum up a lengthy discussion on IRC, we've  
>> reached a consensus:  We'll be using the term "execution unit" do  
>> describe the collection of action, views etc.
>>
>> Pro's:
>>
>> - The term does not imply a specific order on those elements
>> - The term implies a strong relationship between the elements
>> - The term implies collaboration between the elements
>> - The term implies that all together they are executable
>>
>> Con's:
>>
>> None mentioned.
>>
>> If you have something to add, feel free to do so. If you don't,  
>> well, then thanks for listening and have a nice day.
>>
>> felix
>>
>>
>> On Mar 19, 2009, at 11:13 AM, Felix Gilcher wrote:
>>
>>> Hi all,
>>>
>>> while writing the tutorial I came across a naming question that  
>>> I'm unable to answer for myself. How do you guys refer to all and  
>>> everything that's tied to an action. The whole bundle of the  
>>> action itself, the views, the templates, the caching config and  
>>> the validation. It would be really helpful if we had a good name  
>>> for it as it's a concept that we're often talking about.
>>>
>>> I'm looking forward to your answers, the game is on
>>>
>>> felix_______________________________________________
>>> Agavi Dev Mailing List
>>> [email protected]
>>> http://lists.agavi.org/mailman/listinfo/dev
>>
>>
>>
>> _______________________________________________
>> Agavi Dev Mailing List
>> [email protected]
>> http://lists.agavi.org/mailman/listinfo/dev
>
> _______________________________________________
> Agavi Dev Mailing List
> [email protected]
> http://lists.agavi.org/mailman/listinfo/dev


_______________________________________________
Agavi Dev Mailing List
[email protected]
http://lists.agavi.org/mailman/listinfo/dev

Reply via email to