In a previous post, I wrote a bit about how we were starting to improve vector layer behavior. That work has been chugging along in a couple sandboxes. We had a dev talk some time ago about allowing multiple strategies on a single layer. Today I put together an implementation of that idea with a new paging strategy.
This strategy allows for client side paging of vector features for protocols that don’t support it on the server. The paging example loads a batch of 100 geotagged photos from Flickr (thanks FeatureServer) and displays them 10 at a time.
With the paging strategy, we can display manageable batches of features in the browser with protocols (like WFS) that don’t (yet) support paging. This is handy in situations where you’re primarily limited by the renderer (because you’re still stuck parsing whatever number of features you get from the server).