20,741
edits
Generic protocol: Difference between revisions
Jump to navigation
Jump to search
http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg22705.html
(http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg24570.html) |
(http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg22705.html) |
||
| Line 16: | Line 16: | ||
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. | 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. | ||
I think it makes sense (when dealing with live data) for the generic protocol to enter a while loop and read data until there is no more available. That way if the sender is sending at a higher rate or FlightGear gets behind for any reason, FlightGear will get caught up each iteration. This obviously does not work well for file input though, so you'd have to differentiate. | |||
== XML File Layout == | == XML File Layout == | ||