"ace project" <[EMAIL PROTECTED]> wrote: > - Multicasting and broadcasting will NOT be in this > prototype, but base protocol should be able to handle > broacasting (without any change with current specs)
Broadcasting should be there by default - all you need to do is give the peer IP as a broadcast address. > - Another question popped up, what Endian do we want ? Network byte order please. This ensures there are no confusion. Does not require a hack like in X-Plane where the packets are marked (wasting 2x4 byte int's) with the byte order markers. Also, network byte order to native o/s byte order conversion routines are part of the socket API. So no messing around writing custom byte swap routines (on any of these o/s's) when the language does not support it. > - I will post the encaptulation protocols tommorrow, > when I have translated their essence to English (they > are in Dutch atm, anybody wants them in Dutch ?) I can read Dutch without too much of a problem. But then (too my shame) I read and write English better than my native language, never mind Dutch. :-) > - There is another totally different design possible > Delayed transmission, delay EVERYBODY 1 sec and the > will all they exactly 1 sec out of sync. I dont think > its the way to go, but its worth mentioning it. Flying in the past...? Interesting... Curt, how about adding sub space anomolies too FG and get Dave to add support for warp engines. I'm sure we can do some very interesting TNG quantum stuff with this. :-) > BTW 2, don't look at typos, English is *not* my > primary language :) Not a problem. My Klingon spelling is a lot worse. :-) q'apla -- Billy _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
