UML Diagrams for the LoadBalancing sample?
Options
Hey
As I am trying to understand the LoadBalancing code I realised that having UML sequence diagrams of it would help a lot.
I know that I can do it myself but perhaps you already have those UML diagrams. If not I wondered if you would have the time to create the UML "sequence" diagrams.
Of course what I mean by "sequence" includes the events sends between the master, game server and client peers.
I would create the following diagrams:
- From the Master and GameServers creation to their registration with the Master
- Setup of the LoadSheeding (WorkloadController, LatencyMonitor)
- Server to server update event sequence
- From the creation of a GameClientPeer until entering a game
- Sending of an event/operation from the client to server and its response (and from server to client).
- Client logout process
- Shutdown process
IMO this would make the documentation (aka source code) much easier to read.
Thanks,
Steven
As I am trying to understand the LoadBalancing code I realised that having UML sequence diagrams of it would help a lot.
I know that I can do it myself but perhaps you already have those UML diagrams. If not I wondered if you would have the time to create the UML "sequence" diagrams.
Of course what I mean by "sequence" includes the events sends between the master, game server and client peers.
I would create the following diagrams:
- From the Master and GameServers creation to their registration with the Master
- Setup of the LoadSheeding (WorkloadController, LatencyMonitor)
- Server to server update event sequence
- From the creation of a GameClientPeer until entering a game
- Sending of an event/operation from the client to server and its response (and from server to client).
- Client logout process
- Shutdown process
IMO this would make the documentation (aka source code) much easier to read.
Thanks,
Steven
0
Comments
-
Working on it... thanks for the feedback.0
-
Is this work still in progress? Do you have an estimated completion date?0
-
Yes, Loadbalancing documentation is something we still plan to do, but we haven't found time to do it yet - sorry!0