Justin, perhaps you could submit a WFS 2 change request to encourage OGC to change the spec to what you were able to reasonably implement? :-D
-------- Original Message -------- Subject: RE: GeoServer WFS 2.0 limitations Date: Mon, 24 Oct 2011 17:39:58 +0800 From: Simon Cox Submit a WFS 2.0 Change Request to explicitly relax this requirement. https://portal.opengeospatial.org/public_ogc/change_request.php It's just a web form. -----Original Message----- From: Ben Caradoc-Davies Sent: Monday, 24 October 2011 4:56 PM To: Simon Cox Subject: GeoServer WFS 2.0 limitations FYI http://geoserver.org/display/GEOS/GSIP+61+-+WFS+2.0 "WFS 2.0 adds the ability to page results of a GetFeature request via the startIndex and maxFeatures parameters. The WFS specification actually implies that a service must maintain consistent paging results in the light of transactions, but such a restriction is very difficult to implement and implies that the server be able to store large results in memory, or maintain database transactions between requests which goes against the stateless nature of WFS all together. For this reason we ignore this requirement in our implementation." -- Ben Caradoc-Davies <[email protected]> Software Engineer CSIRO Earth Science and Resource Engineering Australian Resources Research Centre ------------------------------------------------------------------------------ The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
