[Seaside] Re: Task Escape

[Zulq Alam]

Thanks Keith.

I'll be honest, the message eating null pattern gives me the fear. Just 
the name sounds apocalyptic to me. :)

In this case, I suppose, it's like the state pattern where each step 
returns the current state?

More explicitly this might be:

MyTask>>#cancel
     state := MessageEater new

MyTask>>#go
     state := self.
     state stepOne.
     state stepTwo.

MessageEater>>doesNotUnderstand: aMessage
     " Yum "
     ^ self

Presumably you could have additional states, although not sure what 
these would be in this abstract example.

Thanks,
Zulq.

Keith Hodges wrote:
> or... you could try a message eating null. I know that people are alway
> suspicious of letting message eating null loose in their code, however I
> do think that in a specific controlled situation it can be very useful.
> 
> You example becomes...
> 
> self stepOne stepTwo stepThree.
> 
> if any of the steps returns Null then the subsequent steps are passed over.
> 
> Null is available in universes.
> 
> cheers
> 
> Keith