Hi Emily I have a couple of ideas; not sure if they are good however. Is this specifically a caching WFS module? Or can it be used to cache any FeatureSource?
My initial idea of integration was to make a service similar to that used for temporary memory datastores. That is a specific entry in the catalog that would hold all the cached datasets. When a GeoResource is cached the dataset would show up here; and the cached dataset would be a friend of the original dataset (so any layer that is drawing the original would have a chance to consider this faster local friend). In terms of holding the code; you could start off as a community module and we could copy the code into udig as it passes code review etc. I know Jesse is worried about the geotools module being unsupported; if you are happy reviewing that code we can also start to copy it into a more mainstream geotools module such as "gt-data". Jody On Fri, Jan 23, 2009 at 8:36 AM, Emily Gouge <[email protected]> wrote: > All, > > I've been working on a georesource that wraps a WFSDataStore and makes use > of the unsupported geotools module gt-caching to cache WFS features client > side. > > I would like to share this work; however I don't want to put in into the > main udig code base as it currently relies on the unsupported geotools > module. I was thinking of making a directory for myself in communities > section of the repo (http://svn.refractions.net/udig/udig/community/) and > adding it there. Is this okay? Does somebody have a different idea? > > Thanks, > Emily > > _______________________________________________ > User-friendly Desktop Internet GIS (uDig) > http://udig.refractions.net > http://lists.refractions.net/mailman/listinfo/udig-devel >
_______________________________________________ User-friendly Desktop Internet GIS (uDig) http://udig.refractions.net http://lists.refractions.net/mailman/listinfo/udig-devel
