On Fri, Sep 30, 2011 at 4:22 PM, <joac...@gmx.de> wrote:
> Am Fri, 30 Sep 2011 16:10:39 -0500
> schrieb Curtis Olson <curtol...@gmail.com>:
>
> > The downside is that this index is used so much in the scenery files
> > that going to a larger int size will have an immediate corresponding
> > proportional impact on the btg sizes of all the files.
>
> Ten years ago 16 Bit hurt much more than 32 Bit nowadays...
>
> And, wouldn't a compressor (tgz, bz2, ...) solve that issue, at least
> for distribution (trafficwise)?
>
That could very well be true ... and I don't think it would be a huge coding
change ... but it should be done in a way that bumps up the btg version
number and picks a new packet id so as to maintain backwards compatibility
with all the existing scenery out there.
Curt.
--
Curtis Olson:
http://www.atiak.com - http://aem.umn.edu/~uav/
http://www.flightgear.org - http://gallinazo.flightgear.org
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2dcopy2
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
