Network Design: Difference between revisions
Jump to navigation
Jump to search
| Line 52: | Line 52: | ||
<uml> | <uml> | ||
class iNetSubscriber { | |||
+{abstract} bool Verify() | |||
+{abstract} void HandleMessage() | |||
} | |||
note right: Abstract base class for message recipients. | |||
iNetSubscriber <|-- MessageManagerBase | iNetSubscriber <|-- MessageManagerBase | ||
MessageManagerBase <|-- MessageManager | MessageManagerBase <|-- MessageManager | ||
MessageManager <|-- NPCManager | MessageManager <|-- NPCManager | ||
MessageManager <|-- ProgressionManager | MessageManager <|-- ProgressionManager | ||
note "Example classes from the server" as Note1 | |||
NPCManager .. Note1 | |||
ProgressionManager .. Note1 | |||
class | class MessageManagerBase { | ||
+bool Verify | +bool Verify() | ||
+void | } | ||
class MessageManager<SubClass> { | |||
+void Subscribe() | |||
+void Unsubscribe() | |||
} | } | ||
class | class NPCManager { | ||
+ | +void HandleMessage() | ||
} | |||
class ProgressionManager { | |||
+void HandleMessage() | |||
} | } | ||
</uml> | </uml> | ||
Revision as of 16:49, 25 December 2012
Design
Classes
Each message from/to server/clients is based on the psMessageCracher that provide interfaces to pack/unpack and print the message.
Server Classes
Sequences
Start up NPCClient
Start up Client
Client Movement
