Thinking out load here . We have created utility classes for a couple far reaching datastore concepts that would otherwise be hard to implement: - we have a locking manager so datastores can manage "wfs style" locks as a wrapper around feature writer access (and do spot checks for any other writing). - we have a "diff map" that can hold any edits in memory (and once again operate as a wrapper around feature reader and feature writer access
Could we present a "Caching" utility class that datastore implementors could lean on? Jody On 06/11/2010, at 10:07 AM, Andrea Aime wrote: > 2010/11/5 Jody Garnett <[email protected]>: >> There is already a module for caching. >> At the geotools level it is willing to cache any datastore; but wfs is what >> it was built for. > > And what it makes sense for. Too slow for anything else, tried it out, > slower than direct > access for both shapefiles and spatial databases ;-) > > Cheers > Andrea > > ----------------------------------------------------- > Ing. Andrea Aime > Senior Software Engineer > > GeoSolutions S.A.S. > Via Poggio alle Viti 1187 > 55054 Massarosa (LU) > Italy > > phone: +39 0584962313 > fax: +39 0584962313 > > http://www.geo-solutions.it > http://geo-solutions.blogspot.com/ > http://www.linkedin.com/in/andreaaime > http://twitter.com/geowolf > > ----------------------------------------------------- ------------------------------------------------------------------------------ The Next 800 Companies to Lead America's Growth: New Video Whitepaper David G. Thomson, author of the best-selling book "Blueprint to a Billion" shares his insights and actions to help propel your business during the next growth cycle. Listen Now! http://p.sf.net/sfu/SAP-dev2dev _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
