[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Objects, processes, and encapsulation
> The most important design pattern in OO is the
Yes, that is a very often used design pattern. Don't forget that the whole
callback business is regarded as a design pattern as well, the 'Publisher-Subscriber'
pattern. That is a pattern that is often (mis)used as well.
>Gerards solution with the ALT does not work very well:
> The View should always be able to receive the
>I'm not sure whether Ians suggestions work: both model
> and view must be able to initiate the communication
> at some arbitrary point in time (in trace :-) )
>In my opinion, the problem should be solved by making
>the ChangeNotification and Asynchronous channel. For
>example, an OverwritingOnePlaceBufferChannel.
Probably most design patterns can easily be changed into process
forms. This could be the beginning of a book, perhaps with title
'Design Patterns: Elements of Reusable Process-Oriented Software'?
But seriously, we could look into process patterns (such as the
client-server model) and try to find out what sort of behaviourial
aspects we can guarantee with CSP.
Dr. Ir. J.P.E. Sunter
PO. Box 80060 / 5600 KA Eindhoven / The Netherlands
Tel. +31-40-2755288 / Fax. +31-40-2755419 / E-mail: johan.sunter@xxxxxxxxxxx
"The distance between insanity and genius is measured only by success."
James Bond, "Tomorrow Never Dies"