Hey Tim, it just came to my mind since I wanted to port all of my application's WFS requests to use Protocol.WFS. I use quite a bit of GET requests where POST is not needed.
But you're right, why not use POST all the time. Best regards, Bart > Hey- > > bart...@osgis.nl wrote: >> Hi list, >> >> are there any plans to support HTTP GET in Protocol.WFS? > > It would be nice to have a property that let you decide if you always > wanted GET. The drawback, of course, is when you've got a filter that > serializes (+ rest of url) to 2083 chars. > > We're you envisioning a property, or some logic that tried to determine > if POST was necessary? > > Also, it's probably worth asking why it makes a difference (aside from > being gross that we have to POST GetFeature). > > Tim > >> >> Best regards, >> Bart >> >> _______________________________________________ >> Dev mailing list >> Dev@openlayers.org >> http://openlayers.org/mailman/listinfo/dev > > > -- > Tim Schaub > OpenGeo - http://opengeo.org > Expert service straight from the developers. > _______________________________________________ > Dev mailing list > Dev@openlayers.org > http://openlayers.org/mailman/listinfo/dev > _______________________________________________ Dev mailing list Dev@openlayers.org http://openlayers.org/mailman/listinfo/dev
