Thanks for putting this patch together Tim. Initially Chris wanted that the bbox strategy behave aggressively on zoom in, but, as an optimization, only if the number of features in the layer is not lower than the maxfeatures value set in the protocol.
The change you're proposing wouldn't allow this. The change I proposed involved adding a new Integer option to the bbox strategy. If that option is null the strategy behaves as currently. If it's non-null then it behaves aggressively if the number of features in the layer is not lower than the option value. Chris was concerned with configuration data duplication - maxfeatures is kinda set in the protocol as well as in the strategy; which doesn't bother me actually. You may concerned with the fact that my proposed option targets a specific case (maxfeatures-parameterized requests) and doesn't address other, maybe more common, cases. I actually don't see other cases when a more aggressive mode makes sense, but that's probably just me. Cheers, Eric 2008/11/13, Tim Schaub <[EMAIL PROTECTED]>: > Hey- > > Christopher Schmidt wrote: >> >> I'm still lost as to how to go about coding what I want :) I want to >> have maxfeatures, and more aggressive invalidation because of it. Any >> suggestinos as to how I might go about implementing that, or should I >> just toss together something and people will look at afterwards? >> > > If you haven't already tossed something together, see the patch for > http://trac.openlayers.org/ticket/1830. > > Set resFactor to 1 if you want to request features with every change in > resolution. > > Tim > >> Regards, > > > -- > 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
