Protocol.MapFish "bbox" property

[adube]

New/Changed "bbox" property in Protocol.MapFish

Description of the issue :

While trying to use the mapfish protocol with featureserver instead of mapfish, we ran in one little problem : mapfish server uses 'box' and featureserver uses 'bbox'.

Solution(s) :

• Have "bbox" as an alias to "box" in mapfish.
• Change the client code (Protocol.Map Fish?) so that "bbox" is used instead of "box", in this way mapfish would be closer to the featureserver interface.

Comments are welcomed

[elemoine]

Alexandre, that'd be great if you could test Protocol.MapFish against FeatureServer again, and report back in this ticket. Thanks,

[adube]

Eric, I confirm that the patch resolve the issue. I hope this see theses changes in trunk soon. Thanks a lot.

[bbinet]

Eric, what should do mapfish server in case it receives both bbox and box params? Which one should it take into account?

If we choose to give priority on bbox to be closer to the featureserver interface, the patch needs minor update.

[elemoine]

Replying to bbinet:

Eric, what should do mapfish server in case it receives both bbox and box params? Which one should it take into account?

I personally don't care. I made "box" have precedence over "bbox" because "box" was there first (sort of backward compatibility)

If we choose to give priority on bbox to be closer to the featureserver interface, the patch needs minor update.

You review you choose ;-) Either way's fine with me.

[bbinet]

patch-MapFish-496-r2729-A1.diff is minor update to ignore "box" if "bbox" is present instead of overwriting it.

This is also making "bbox" have precedence over "box" because "bbox" has been chosen as default on client side.

If you're ok with this, please commit.

[elemoine]

(In [2731]) Protocol.Map Fish? "bbox" property, r=bbinet (closes #496)