#11 plausibilty validation filters

[Anonymous]

for the long-term future of flightgear multiplayer support it would be desirable if there was a way for server administrators to set up filters to validate aircraft state before propagating it to connected clients, this could be a very simple but effective way to ensure that multiplayer traffic is never tainted, i.e. there could be a mapping of properties specifying valid flight regimes, or rather valid flight profiles for a given aircraft, consisting of data such as:

- min/max airspeed
- max sink rate
- max climb rate
- max bank rate
- max turnrate

and others

This could help server administrators to optionally avoid a Cessna C172 joining the multiplayer server and flying mach 3 or climbing at 5000fpm.

Of course this should be kept entirely optional, maybe even as a separate instance of the current server code which applies the filter

[Nobody/Anonymous]

Logged In: NO

such a filter framework, if coupled with an interface to the terrain database, would also be useful to optionally prevent positional aircraft data being transmitted if it starts getting below the terrain boundaries, i.e. to support "crash" detection; basically resulting in such occurences terminating a multiplayer session. However, this should probably be kept optional or at least configurable, because there are meanwhile now different types of non-aircraft vehicles supported, for which it might be valid to go below the terrain layer (i.e. think ship)

[Nobody/Anonymous]

Logged In: NO

yes, if there could be a query such as aircraft.agl <= 0.00 data could be automatically discarded

[Nobody/Anonymous]

Logged In: NO

validation filters should probably be kept separate from the core server code, so that it doesn't add to the complexity of the current code.