Not 'closed off forever', but check the actual performance: do you need this feature?
On 28 May 2010 23:25, "SpoilsportMotors" <[email protected]> wrote: On May 27, 7:21 pm, Ben Appleton <[email protected]> wrote: > The v2 encoding scheme did 2 things:... Mmm. We'd been using the bejeebers out of both 1 and 2 at v2. I can either compress the data myself, or enable gzip on JSON (which I think is fraught with peril of its own) to resolve (1). It's slightly irksome, but not hideous. With respect to (2), we'd be been using RDP at the server to optimally encode the polylines / polygons for each zoom level, which had the nice side-effect of throwing out points that wouldn't be seen, even at zoom level 20. While I appreciate that V3 will now do that calculation for me, it would be more efficient if I could pre-compute them *once* on the server side, resulting in less work every time a client asks for the polyline or polygon in question. Is this really closed off forever - Google is never going to allow pre-computed polylines? Herb. -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript AP... -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.
