Thorsten> I'm currently looking into an overhaul of the replay
    Thorsten> system. The buffer mechanisms of the existing replay
    Thorsten> system itself won't change, but I'm replacing the
    Thorsten> hard-coded recorder/FDM interface. Instead, I'll

[...]

    Thorsten> I have a working prototype, but nothing ready to be
    Thorsten> committed.  Meanwhile, constructive comments/ideas are
    Thorsten> welcome.

As maintainer of Atlas, an item long on my "to-do" list is improving
the FlightGear/Atlas communications protocol.  At the moment, Atlas
can use two protocols, called Atlas and NMEA.  Both are preset, fairly
limited, and hard-coded.  Ideally, a protocol should be able to send a
richer set of information, and be configurable on a per-aircraft (or
per-user) basis.  Your posting about the replay system made me wonder
if it could be adapted to be such a protocol.

Right now, Atlas' requirements are:

- UDP transmission - FlightGear talks to Atlas via UDP.  UDP packets
  are limited to a theoretical maximum of 64kB, and probably a much
  smaller real-life maximum (although I need to test this).  So the
  protocol can't send over everything and the kitchen sink.

- File streaming - Instead of sending directly to Atlas, FlightGear
  should also be able to dump the data to a file to be read by Atlas
  later.

- Custom properties - It's possible Atlas will want to look at
  properties the replay system doesn't supply, or ignore properties
  the replay system supplies.  It would be nice to be able to specify
  properties that are specific to Atlas (or have Atlas specify them
  all, if that works out better).

What do you think?  Could the replay system be generalized in such a
way?

Thanks,
Brian

------------------------------------------------------------------------------
Using storage to extend the benefits of virtualization and iSCSI
Virtualization increases hardware utilization and delivers a new level of
agility. Learn what those decisions are and how to modernize your storage 
and backup environments for virtualization.
http://www.accelacomm.com/jaw/sfnl/114/51434361/
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Reply via email to