20,741
edits
Generic protocol: Difference between revisions
Jump to navigation
Jump to search
http://www.mail-archive.com/flightgear-devel@flightgear.org/msg32560.html
No edit summary |
(http://www.mail-archive.com/flightgear-devel@flightgear.org/msg32560.html) |
||
| Line 1: | Line 1: | ||
{{PropertyTree}} | {{PropertyTree}} | ||
The ''generic'' communication protocol for FlightGear provides a powerful way of adding a simple ASCII based or binary input/output protocol, just by defining an XML encoded configuration file and placing it in the [[$FG ROOT]]/Protocol/ directory. | The ''generic'' communication protocol for FlightGear provides a powerful way of adding a simple ASCII based or binary input/output protocol, just by defining an XML encoded configuration file and placing it in the [[$FG ROOT]]/Protocol/ directory. | ||
The generic protocol can be easily set up for both input and output. And it supports not just a single medium, but can be easily made to use files, FIFOs, sockets etc. The generic protocol is really good for things like exporting to a delimited ascii file for import into excel for instance. | |||
== XML File Layout == | == XML File Layout == | ||