Re: sequence diagram for observer pattern
- From: "chandra.somesh@xxxxxxxxx" <chandra.somesh@xxxxxxxxx>
- Date: 29 May 2006 10:11:15 -0700
responding to all
Actually the intent of representing the behavior of observer pattern
using sequence diagram was to mine instances of Design
Patterns(observer in this case) from some legacy code...the constraint
that i put on the behavior is that once the state of Subject
changes..then all its Observers are informed of this change..and each
Observer is sent the update message only ONCE for a single change of
state in the subject...To achieve this i can wrap each update message
inside an "alt" structure and further put this entire structure inside
a "loop" block.....this scheme basically takes care of the order
independence problem...however with the above schema we can have
observers being send zero or more update messages.
I would like to know if this is a valid constarint to put on the
behaviour of observer pattern or we can have an observer receiving more
than one update message per state change of subject?
thanks for all the replies
.
- Follow-Ups:
- Re: sequence diagram for observer pattern
- From: H. S. Lahman
- Re: sequence diagram for observer pattern
- From: chandra.somesh@xxxxxxxxx
- Re: sequence diagram for observer pattern
- References:
- sequence diagram for observer pattern
- From: chandra . somesh
- Re: sequence diagram for observer pattern
- From: H. S. Lahman
- sequence diagram for observer pattern
- Prev by Date: Re: Facade
- Next by Date: Re: Searching OO Associations with RDBMS Persistence Models
- Previous by thread: Re: sequence diagram for observer pattern
- Next by thread: Re: sequence diagram for observer pattern
- Index(es):
Relevant Pages
|