On Fri, 21 Oct 2011, Tobias Pape wrote:

>
> Am 2011-10-21 um 01:22 schrieb Levente Uzonyi:
>
>>>
>>> Which leads me right back to my question:  If I have to look at each
>>> kind of Notification to see how it works, then someone please tell me
>>> what type of exception is this "organizing superclass" organizing?
>>> There should be some commonality to all of its subclasses, what is it?
>>
>> Maybe it's worth separating the Notifications which just provide some information and can simply be resumed from those which are used for communication across the stack.
>
>
> Among these ?communication notifications? is the Seaside WADynamicVariable,
> wich leads me to the impression, that?since there are now Thread-local based
> dynamic variables in trunk?communication notifications can be re-modeled
> to be actual dynamic variables (which some of them seem to be)

Yes, some of them can easily be changed to use DynamicVariable (if the 
communication direction is bottom to top and no lazy initialization 
is involved), but others are a bit tedious to implement this way. I think 
the best solution would be to separate these communication exceptions from 
Notification by creating a new subclass of Exception for them.


Levente

>
> Best
> 	-Tobias
>