[Seaside] WATask, anyone?

[Reza Razavi]

On 9/16/12 3:53 PM, Philippe Marschall wrote:
> On Fri, Sep 14, 2012 at 4:31 PM, SebastianHC
> <sebastian_heidbrink at yahoo.de>  wrote:
>    
>> (...)
>> Why is WATask so rearly used and mentioned?
>>      
> Maybe because you can get the same functionality with a method or
> block and #call: without having to create a class.
>    
Yes, indeed. WATask provides a cool medium for coding in Smalltalk the 
flows of control and data among Seaside components that are 
sophisticated enough to "justify" a dedicated class. Otherwise, "a 
method or block and #call: without having to create a class" appears 
sufficient.

Let me add that, to the best of my knowledge, the uniqueness of Seaside 
resides in the #call: mechanism, and not WATask. In my IWST'2010 paper 
("Web Pontoon"), I typically explain how WATask may be replaced by a 
sort of workflow mechanism that leverages the power of #call: to allow 
postponing to run-time the definition of data and control flows among 
different type of components (including Seaside ones). This applies when 
such flows are subject to runtime modifications, to adapt to changing 
user conditions and needs in time and space, without system redesign and 
coding (adaptiveobjectmodel.com).

Cheers,
Reza