So I don't think anyone ever claimed that GWC was officially supporting the WMS Tiling Client recommendation, and indeed it'd be impossible to be anything like 'compliant' as there is no test engine. And it's not even an OGC spec, it's an ad hoc spec made by a (great) crew of Open Source types.
The main driving reason to integrate GWC to GeoServer is to run the new KML super overlay stuff, which actually has little to do with the tiling client recommendation. The integration is pretty loose though, I don't think it'd be right to modify the main GeoServer WMS capabilities document with a vendor specific extension that most WMS clients don't support. I could see having an alternate URL, like ?request=GetCapabilities&tiling=true to return a special caps document with the tiling stuff. But putting even that in while we're in RC status seems to be high risk, it's a new feature, not a bug. Could be good for 1.7.1 I was thinking of trying to push some other GWC integrations then, like having GeoServer's in memory tile cache also check the GWC cache. If you really think inclusion of GWC in its present state would encourage clients that are not correct I think the thing to do would be to just remove GWC's capabilities document. It would have been a lot better to raise this objection earlier, I don't think anyone else was thinking that fully implementing the tiling client recommendation should be a requirement. It's still quite valuable as a caching engine for KML stuff, and for people to point openlayers at. The thing to do seems to be to get GWC to properly implement the capabilities document, to engage with that community, instead of hacking something in to GeoServer caps during a feature freeze. Chris Jody Garnett wrote: > Earlier we talked about including GWC in the GeoServer .1.7.x bundle; at > the time I was all for it - adding additional modules to our sample app > is a good idea. > > Today I actually got to run GWC and have found there is no way to use it > correctly; that is the server is incomplete at this time. > I have created a bug report here: > - http://jira.codehaus.org/browse/GEOS-2173 > > But the bug report amounts to a clarification on this page: > - http://wiki.osgeo.org/wiki/WMS_Tiling_Client_Recommendation > > The WMSC idea is an addition to an existing WMS; as such we need to add > some TileSet information to the VendorSpecificCapabilities. As written > GWC is not producing a valid WMT_MS_Capabilities document (and I cannot > use it for my uDig project). > > Since I am working for a customer on GWC support I am looking into how > to fix this real soon/right now. > > My best idea is to see if the GWC community module can contribute an xml > fragment to the WMS capabilities document; as such I would like to have > this functionality ready for the 1.7.x release. At the very least we > should not include GWC in its current state; it would promote the > development clients that are not correct. > > I will be available to chat about this in the meeting tomorrow. > > Jody > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Geoserver-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/geoserver-devel ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
