--- Melchior FRANZ wrote:
> * Maik Justus -- Wednesday 03 October 2007:
> > The actual MP code does not send all properties of the static list. It
> 
> > only sends those properties, which are existing at initializing of the
> 
> > MP-code. Thats why you need to define some properties within the 
> > -set.xml file [...]
> 
> Ahh, thanks for the clarification. That's good news. (Although
> I still get too much data in. Guess I need to play with the
> interval then.  :-)
> 
> It would, nevertheless, be good to have ways to transfer larger
> junks of data (such as file paths), and not have them sent in
> every single package.

... like all the chat data, which is currently included in every packet :(

Part of the problem of course is that with UDP we can't rely on the
receiver having received the previous message. 

I guess one option might be to distinguish between "core" data (position,
attitude, speed etc) which we want to be accurate, and "nice to have" data
which is not so time- or function- critical (chat text).

This latter data could be transmitted when it changes, and every (say) 5
seconds. We could then use a more flexible message format - for example
one which encodes the property name and value. The properties to be
exported in this way could then be indicated by an XML attribute.

For something like livery names, the end-user is not really going to
notice if the data is only updated irregularly, while it should stop the
average message size from increasing too much.

-Stuart




      ___________________________________________________________
Yahoo! Answers - Got a question? Someone out there knows the answer. Try it
now.
http://uk.answers.yahoo.com/ 

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Reply via email to