I have done another round of research and revised the page accordingly. A couple of design decisions of note: - use of ServiceInfo and ResourceInfo from the start - use of Memento to allow for hosting application to preserve state - breakdown of TileServer, TileMap, TileSet as per OSGeo reference model - TileRange serving as a async request that can smoothly be hosted ontop of a cache, progress monitor reports back as tiles are avaialble, Set of GridCoverage is always available and valid (just may be transparent or approx before load is completed)
Jody > Jody Garnett ha scritto: >> If I can ask a PMC member to review this before I start up an >> unsupported module. (Note: rgould has already looked it over based on >> his WMS experience). >> - http://docs.codehaus.org/display/GEOTOOLS/Tile+Server+Client > > Well, the page says many things, but not what TileServer is supposed > to be. I guess it will be a generic client interface that allows us > to access remote tile servers, right? > So, it will be analogous to the WMS module, right? > > I still haven't read the tiling spec, but what strikes me a little as > odd, is that these interfaces seem to address just one pyramid... > is a tiled map server designed to serve just one, compared to the > wms spec where you can specify multiple layers/maps? > > 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
