CMSI 698 SS:NVE Summer I 2004 - Zone Manager I

Requirements

Zones track which Entity IDs are under the control of which client connections
Zone Managers construct BES messages from received AES messages and forward those to peers every 100ms
Subsequent BES messages relating to the same entity in outbound queues replace earlier ones
Master Zone proactively notifies clients sending AES messages to it if a new SubZone comes online which can service its needs
SubZones transmit error messages to Connected Clients sending AES messages outside of the SubZone's area of control
SubZones transmit unsolicited Zone Announcements to clients sending AES messages outside of the SubZone's area of control

Two modes of operation, zone master and sub-zone
Sub-Zones launched with parameters for x1,y1,z1 x2,y2,z2 and IP:port of master zone
Sub-zones establish TCP sesion with master zone and exchange Zone Announcement and Zone Queries
TCP Session established with all other Sub-Zone servers
Answers zone partition information queries
Re-transmits received UDP messages to all UDP clients
Maintains database of all known UDP clients by IP:PORT and the last time they were heard from
UDP Messages received are queued and flushed over TCP connection every 100ms
Messages received over TCP connection are transmitted to all known UDP clients
'Known' UDP clients time-out if not heard from in 120 seconds
Command-line only
Any language
Any platform