On Donnerstag 28 Juli 2005 18:32, Andy Ross wrote:
> Oliver Schroeder wrote:
> > Andy is, of course, right. We should not send binary data over the
> > wire and I think that using XDR for transmission
>
> Binary is fine. Uncooked memory is not. :) And FWIW, XDR seems
> awfully heavyweight to me. It involves a comparatively large amount
> of code for things that are really pretty easy, while at the same time
> making hand optimization of the packet format more difficult.
>
> Note that this hand tuning can be really beneficial, especially if the
> server is on a low bandwidth link. The multiplayer protocol I was
> thinking of (which these days is, I guess, mostly an idea box for the
> working version) managed to pack a full precision* position, velocity,
> acceleration, orientation and rotation rate into a block of 26 bytes.
>
> * Positions to within 1mm, orientations to within a degree over a
> typical inter-packet delay.
>
> That's about 3x smaller than a naive implementations based on floats
> and doubles, which means that you can transmit data on 3x as many
> aircraft/objects over the same link.
Well, I was looking for an existing implementation of a non ascii format
which will just work.
Looking at that stuff I have found is not that heavyweight. That is just a kind
of iostream like implementation to build up that network packets in a defined
byte order and alignment. That would be just handy to use ...
But if you have a better solution ...
Greetings
Mathias
--
Mathias Fröhlich, email: [EMAIL PROTECTED]
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
