pull specific filterToParams method out of HTTP protocol

[tschaub]

The filterToParams method on the HTTP protocol is specific to MapFish (as far as I know). We should make it obvious that it can be configured with an alternate method. In addition, the same method should be available to other protocols (e.g #2956).

[tschaub]

pull out MapFish filterToParams serializer

[tschaub]

Tests pass. With this, the original behavior of the HTTP protocol is preserved. It also allows custom builds to exclude the MapFishFilterSerializer and app devs to provide their own filterToParams method.

Thanks for any review.

[bartvde]

See also the discussion at:

 http://osgeo-org.1803224.n2.nabble.com/script-protocol-and-filter-serialization-td5967792.html

[crschmidt]

This looks good. The naming is not that important. After all, we're still making people use OpenLayers.LonLat :) maybe someday us server devs can sit down and give this filter type a name, but until then, let's roll with this.

Attaching a new patch to fix conflicts, but other than that, this looks solid, tests pass, please commit.

[crschmidt]

Ignore the .2. patch, grab the .3. :)

[tschaub]

extracting the simple filter serializer

[tschaub]

Given that this is used in more than one place, I think we agree a more general name makes sense. I've updated the patch to name this "SimpleFilterSerializer."

I hope this meets with approval.

[tschaub]

(In [11673]) Adding a filterToParams method on the HTTP protocol. This allows you to specify how a filter is serialized in HTTP feature requests (using CQL for example). By default, we use the OpenLayers.Protocol.simpleFilterSerializer method. r=crschmidt (closes #3032)