Event Handling Design: Difference between revisions

Latest revision as of 17:55, 9 April 2013

Event handling is a speciall case of the Detailed Network Design where messages are published and received inside the server.

A Message handler has a list of subscriptions.

Each server class inherit from the iNetSubscriber.

@@ Line 5: / Line 5: @@
 === Classes ===
+{|
+|
+A Message handler has a list of subscriptions.
+|
 <uml>
@@ Line 25: / Line 30: @@
 </uml>
+|
+Each server class inherit from the iNetSubscriber.
+|
 <uml>
@@ Line 42: / Line 51: @@
 class MessageManagerBase {
     +bool Verify()
+   +bool HandleMessage()
 }
@@ Line 50: / Line 60: @@
 class ServerClass {
-    +void HandleEvent()
+    +void HandleTestEvent()
 }
 </uml>
+|}
 === Sequences ===
@@ Line 60: / Line 72: @@
 <uml>
+ServerClass -> ServerClass : Subscribe
+note right : Subscribe to TestEvent
+activate ServerClass
+deactivate ServerClass
 ServerClass -> MsgHandler : Publish
+note right : Publish the TestEvent
+activate ServerClass
+activate MsgHandler
+loop All Subscriptions
 MsgHandler -> MsgEntry : Reset
-MsgHandler -> iNetSubscriber : Verify
+activate MsgEntry
-MsgHandler -> iNetSubscriber : HandleMessage
+MsgEntry --> MsgHandler
+deactivate MsgEntry
+MsgHandler -> ServerClass : Verify
+activate ServerClass
+ServerClass --> MsgHandler
+deactivate ServerClass
+MsgHandler -> ServerClass : HandleMessage
+activate ServerClass
+ServerClass -> ServerClass : HandleTestEvent
+activate ServerClass
+ServerClass --> MsgHandler
+deactivate ServerClass
+deactivate ServerClass
+end
+MsgHandler --> ServerClass
+deactivate MsgHandler
+deactivate ServerClass
 </uml>