Magodra: /* Design */

2013-04-09T17:56:06Z

Design

← Older revision		Revision as of 17:56, 9 April 2013
Line 1:		Line 1:
	== Design ==		== Design ==
	This page describe the details in the network transport layer of Planeshift. For message follows between the Server/Clients see the [[Network Design]] page. A subset of the Detailed Network Design is the internal Server [[Event Handling]].		This page describe the details in the network transport layer of Planeshift. For message follows between the Server/Clients see the [[Network Design]] page. A subset of the Detailed Network Design is the internal Server [[Event Handling Design]].

	===Classes===		===Classes===

Magodra: /* Design */

2013-01-02T18:58:32Z

Design

← Older revision		Revision as of 18:58, 2 January 2013
Line 1:		Line 1:
	== Design ==		== Design ==
	This page describe the details in the network transport layer of Planeshift. For message follows between the Server/Clients see the [[Network Design]] page.		This page describe the details in the network transport layer of Planeshift. For message follows between the Server/Clients see the [[Network Design]] page. A subset of the Detailed Network Design is the internal Server [[Event Handling]].

	===Classes===		===Classes===

Magodra: Created page with "== Design == This page describe the details in the network transport layer of Planeshift. For message follows between the Server/Clients see the Network Design page. ===C..."

2013-01-02T18:52:02Z

Created page with "== Design == This page describe the details in the network transport layer of Planeshift. For message follows between the Server/Clients see the Network Design page. ===C..."

New page

== Design ==
This page describe the details in the network transport layer of Planeshift. For message follows between the Server/Clients see the [[Network Design]] page.

===Classes===
<uml>
class psMessageCracker {
+SendMessage()
+FireEvent()
+ToString()
}

psMessageCracker <|-- NPCAuthent
psMessageCracker <|-- MsgStrings

psMessageCracker *-- MsgEntry : msg
MsgEntry *-- psMessageBytes : bytes
</uml>

Each message from/to server/clients is based on the psMessageCracher that provide interfaces to pack/unpack and print the message.

<uml>

MsgHandler "1" *-- "0..N" Subscription : subscribers
MsgHandler "1" *-- "1" NetBase : netbase
MsgHandler "1" *-- "1" MsgQueue : queue
NetBase "1" *-- "0..N" psNetPacketEntry : packets
NetBase "1" *-- "1" NetPacketQueue : NetworkQueue
NetBase "1" *-- "0..N" NetPacketQueue : senders
NetBase "1" *-- "0..N" MsgQueue : inQueues
NetBase "1" *-- "0..N" psNetPacketEntry : awaitingack
psNetPacketEntry "1" *-- "1" psNetPacket : packet

class Connection {
+uint32_t sequence
}

MsgQueue "1" *-- "0..N" MsgEntry
NetPacketQueue "1" *-- "0..N" psNetPacketEntry

MsgHandler <|- ClientMsgHandler
ClientMsgHandler "1" *-- "1" OrderedMessageChannel : orderedMessages

OrderedMessageChannel "1" *-- "0..N" MsgEntry : pendingMessages
NetBase <|- psNetConnection
psNetConnection *-- MsgQueue : inQueue
psNetConnection *-- Connection : server

Subscription "1" *-- "1" iNetSubscriber : subscriber

</uml>

==== Server Classes ====

<uml>
class iNetSubscriber {
+{abstract} bool Verify()
+{abstract} void HandleMessage()
}
note right: Abstract base class for message recipients.

iNetSubscriber <|-- MessageManagerBase
MessageManagerBase <|-- MessageManager
MessageManager <|-- NPCManager
MessageManager <|-- ProgressionManager
note "Example classes from the server" as Note1
NPCManager .. Note1
ProgressionManager .. Note1

class MessageManagerBase {
+bool Verify()
}

class MessageManager<SubClass> {
+void Subscribe()
+void Unsubscribe()
}

class NPCManager {
+void HandleMessage()
}
class ProgressionManager {
+void HandleMessage()
}

</uml>

===Sequences===

[[Category:Engine documents]] [[Category:NPCClient Design]] [[Category:Server Design]]

Detailed Network Design - Revision history

Magodra: /* Design */

Magodra: /* Design */

Magodra: Created page with "== Design == This page describe the details in the network transport layer of Planeshift. For message follows between the Server/Clients see the Network Design page. ===C..."