Revert the FlightGear network protocol to v24 #1234
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The FlightGear ticket 2313 has introduced a change in the FlightGear network protocol which broke backward compatibility with the then current version 24. That forced us to support a new version of the protocol via the commit b42f423. Unfortunately the support of the new protocol did not work well (see issue #325) and the code to support both protocol versions 24 and 25 was ugly.
It was later discovered that the new network protocol was also breaking the interface between Simulink and FlightGear (see FlightGear ticket 2742) so the decision has been made by the FlightGear developers to drop the protocol version 25 and revert it back to 24.
The network protocol version 25 has never been part of an official FlightGear release so reverting it back to 24 is not breaking backward compatibility.
This PR reverts the commit b42f423 since the support of the protocol version 25 is now meaningless. This should fix the issue #325 in the process.