Difference between revisions of "Event Handling Design"
Jump to navigation
Jump to search
m (moved Event Handling to Event Handling Design) |
|||
| (2 intermediate revisions by the same user not shown) | |||
| Line 5: | Line 5: | ||
=== Classes === | === Classes === | ||
{| | |||
| | |||
A Message handler has a list of subscriptions. | |||
| | |||
<uml> | <uml> | ||
| Line 25: | Line 30: | ||
</uml> | </uml> | ||
| | |||
Each server class inherit from the iNetSubscriber. | |||
| | |||
<uml> | <uml> | ||
| Line 56: | Line 65: | ||
</uml> | </uml> | ||
|} | |||
=== Sequences === | === Sequences === | ||
| Line 72: | Line 83: | ||
MsgHandler -> MsgEntry : Reset | MsgHandler -> MsgEntry : Reset | ||
activate MsgEntry | activate MsgEntry | ||
MsgEntry --> MsgHandler | |||
deactivate MsgEntry | deactivate MsgEntry | ||
MsgHandler -> ServerClass : Verify | MsgHandler -> ServerClass : Verify | ||
Latest revision as of 19:55, 9 April 2013
Event Handling
Event handling is a speciall case of the Detailed Network Design where messages are published and received inside the server.
Classes
|
A Message handler has a list of subscriptions. |
|
Each server class inherit from the iNetSubscriber. |
|
Sequences