| 1 | = Network Abstract = |
| 2 | [[ArchivePage]] |
| 3 | |
| 4 | This module defines an overall interface to the network for all modules in Orxonox. The design has to match the Feature Requests, which are served best, if the architectural requirements are met. |
| 5 | |
| 6 | |
| 7 | Features: |
| 8 | * Synchronize any object on one client side to the other |
| 9 | * File download (for maps, sounds etc. - Halflife 2 Style) |
| 10 | * Server/Client Architecture |
| 11 | |
| 12 | |
| 13 | Architectural Requirements: |
| 14 | * Interface |
| 15 | * Simple and generic architecutre |
| 16 | * Easy to adapt, extend and use |
| 17 | * Abstraction of a network connection to a network binary stream (data streams) |
| 18 | * Data Streams |
| 19 | * Java style data streams |
| 20 | * Pipes |
| 21 | * Buffered Streams |
| 22 | * Network Monitoring |
| 23 | * Bandwith, Delay measurement -> Connection quality |
| 24 | * Firewall detection (matters only for UDP) |
| 25 | * Data flow measurement |
| 26 | * Multiple Network Protocol Support |
| 27 | * TCP/UDP mode for sending, reciving data |
| 28 | * Multiple internal protocols |
| 29 | * Network Architecture |
| 30 | * Star topoligy (one server, multiple clients) |