Martin Desruisseaux ha scritto: > [EMAIL PROTECTED] a écrit : >> Thiking about it, but this feels like a bug to me... now I know the >> problem, and know how to avoid it, but >> it's very counter intuitive that an object gets kept into memory when >> all client code that refers >> to it released its references. What do you think? > > Starting with Geotools 2.3, this problem should not occur anymore > since FactoryFinder.getFooFactory(Hints) should returns a shared > factory instance even in the case of non-empty hints. We should not > have anymore hundred of CoordinateOperationFactory objects floating > around after every FactoryFinder.getCoordinateOperationFactory(hints) > calls. > Nice... was thinking about the BufferedCoordinateOperationFactory and the like. I'm wondering, why doesn't CRS use BufferedCoordinateOperationFactory and the other Bufferedxxx class? This would make it a central point were all transformation needs can be solved with good performance and optimal sharing. Usually applications use a limited set of CRS and trasformations among them, it makes sense to cache them in my opinion. And even if they may grow for some app, this would not be a problem if the cache is based on soft references, or hard references with limited size. Makes sense?
Cheers Andrea ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
