On Thu, 8 Oct 2009, Vivian Meazza wrote: > Way back in the early iterations of MP we had 2 sorts of messages - those > which were transmitted on every cycle, and those which were transmitted on > change of data. The trouble with that is with clients joining and leaving, > it is hard to ensure that the clients are up-to-date. So you need to re- > transmit on clients joining, which means triggering the originating client > etc. etc. I think for that reason it was abandoned. It's just easier and > more reliable to transmit everything all the time. And actually, the end > result in data transmitted terms turns out to be not that different.
Yes, that is one issue. The approach I aimed for the last time I tried to mess with the MP subsystem was to send properties on change (perhaps repeated Y times) and every X seconds (to update newly joined users and cover lost packets). That seemed to be simple enough that it could even be backwards compatible - but unfortunately it caused occasional failures in the property interpolation code on the receiving side that I didn't manage to sort out. Going in that direction could be a feasible way to reduce the bandwidth consumption, though. Cheers, Anders -- --------------------------------------------------------------------------- Anders Gidenstam WWW: http://www.gidenstam.org/FlightGear/ ------------------------------------------------------------------------------ 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
