>> Futhermore, we want our implementation to address the problem of
>> limited memory, e.g. we want to offer an interface for later
>> possibility of storing some geometry data in order to relieve the
>> limited memory capabilities (for example a Factory which returns
>> Lists os some GM_xxx objects, the list can be implemented
>> persistent afterwards).
>>
This part sounds a bit strange to me, I imagine you have some feedback
from Martin? It would
make more sense to store a Go-1 "Graphic" where you are saving out some
Geometry+Style
information...
We didn´t discuss this approach with many people yet, though Martin already knows about it. We neither spent too much time in it. Since i don´t have much experience with persistence in Geometries, that was one of our most simple ideas.
I am not very familiar with the GO-1, but we are open for all types of suggestions.
Cheers,
Sanjay
------------------------------------------------------------------------- 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
