O.K. - I was thinking about our memory problem some more last night and this morning. (I know I should just let this go...)
I remembered that JUMP/OpenJUMP uses a separate renderer for each layer. We should be able to create a new renderer that renders our layers that wrap ram-independent implementations of the FeatureCollection interface. This new renderer wouldn't keep all of the features in the memory after it had painted the map screen. The other layers would use JUMP's built-in renderers, perserving the speed for smaller data sets. What do you guys think about this possibility? The Sunburned Surveyor ------------------------------------------------------------------------- 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 _______________________________________________ Jump-pilot-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
