Justin, I think that the only obligation on a service that implements the paging profile is to specify in its capabilities document whether paging is consistent across transactions (7.7.4.4.2.1). Just set this to false and you are done.
Kind regards, Ben. On 22/02/12 23:35, Justin Deoliveira wrote: > Hey Ben, > > Sorry for the late response. But if you look at Table 14 of the spec (section > 8.3.5.3, page 53) you will notice a service constraint named > "PagingIsTransactionSafe", which is described as: "Specifies whether the > server maintains transactional consistency between paging iterations". > > It is possible i am misunderstanding what this implies. > > On Tue, Feb 21, 2012 at 1:52 AM, Ben > Caradoc-Davies<[email protected]> wrote: > Justin, > > the only outstanding issue I can find in GSIP 61 is the bit where you say: > > "WFS 2.0 adds the ability to page results of a GetFeature request via the > startIndex and maxFeatures [sic, I think you mean count] 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." > http://geoserver.org/display/GEOS/GSIP+61+-+WFS+2.0 > > I can't find anything in the spec that *requires* consistent paging results > across transactions (but then I know transactions least of all). Or do you > think it is just a convenient omission? I can see why it would make sense, > and also why it would be prohibitive to implement. > > Next SWG meeting is on Wednesday; still time for me to squeeze in a last > minute change request if necessary (for WFS 2.1). > > Kind regards, > Ben. > > > > On 01/02/12 14:07, Ben Caradoc-Davies wrote: > Justin, > > the working group is yet to receive all the change requests and has been > discussing which to discuss [1]. Looks like there are some that are > similar to your concerns. When I have them, I will compare the change > requests to GSIP 61 and see if there are any outstanding issues. > > Kind regards, > Ben. > > -- > Ben Caradoc-Davies<[email protected]> > Software Engineer > CSIRO Earth Science and Resource Engineering > Australian Resources Research Centre > > > > -- > Justin Deoliveira > OpenGeo - http://opengeo.org > Enterprise support for open source geospatial. > > -- Ben Caradoc-Davies <[email protected]> Software Engineer CSIRO Earth Science and Resource Engineering Australian Resources Research Centre ------------------------------------------------------------------------------ Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
