Jody Garnett ha scritto: > In talking to Frank today I learned that gdal is trying to push 1.7 > out the door; as I understand it (from a conversation at foss4g) we > are hanging back a version due to memory leaks.
Due to unforeseeable instability actually. GDAL is well tested in its own common case, which is short usage: generally speaking desktop apps don't run more than a few hours, and MapServer is more often than not running without fastcgi enabled. Even when it is a segfault brings down one worker, which is promptly replaced by the FastCGI runtime. When it comes to GeoServer we have a single process running for weeks or months. If it segfaults the service goes down, period. It's much a more demanding working environment. That means we need to test it a lot more and it makes sense to use releases that are known to be very stable to start with, also given time is usually short and thus there is none to be spent debugging GDAL proper (the bindings themselves have to be debugged/improved to start with). Only Simone and his crew have the skill to port the bindings to GDAL 1.7 and at the moment, afaik, are working on a port towards 1.6. Not sure if he has any time to check out 1.7, I cannot answer for him. Just trying to explain that this is not as easy as it may seem. Cheers Andrea -- Andrea Aime OpenGeo - http://opengeo.org Expert service straight from the developers. ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
