20,741
edits
FGAIS: Difference between revisions
Jump to navigation
Jump to search
→Design
(→Design) |
|||
| Line 24: | Line 24: | ||
== Design == | == Design == | ||
Thinking about it, the best option would probably be forking fgms and implementing this as part of a custom fgms fork - that way, it could be either configured as a relay by existing servers, or simply used as an additional MP server at the client-side, so that the MP system in FG would only need to support multiple concurrent fgms connections to different servers. That way, we wouldn't be overloading the main fgms network, but just have an additional network of fgms servers that use real traffic feeds | |||
So it would make sense to start moving the implementation to the fgms side of things - and away from the client. | |||
That would allow us to have a single fgms instance, just for aircraft/vessel traffic - without doing all the parsing at the client side. | |||
== Related == | == Related == | ||