On 8 Oct 2009, at 18:08, Anders Gidenstam wrote: > The way the MP protocol is done now you really really do not want to > do > that by creating a new MP enabled string property and put the flight- > plan > in it. Not only is the string encoding horribly inefficient (a 32bit > word > per character) but it would also be sent in each and every packet.
That sounds bad :) > >> Is there an 'event' channel in MP, to deal with properties which >> change infrequently? (Compared to position/velocity/surface >> positions/ >> etc) > > No, there isn't but this might be time to create one. There is a > rather complicated Nasal module for that kind of communication in > Nasal/mp_broadcast.nas which utilizes a MP enabled string property > (but > send the relatively short empty string, "", when nothing is going on. Eurgh, that sounds bad too. The 'usual' way to handle this would be to interleave the current update packets with 'event' packets, for properties that change more slowly. Using a sequence number for each event packet, and using the regular update packets to send the current sequence number, it's possible to make the event packet delivery reliable - without incurring the overhead (or complexity) of TCP. There's quite a lot of improvements that could be made to higher levels of MP, if arbitrary properties could be synchronised over MP :) Regards, James ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
