On Tue, Feb 2, 2010 at 12:40 AM, bratliff <[email protected]> wrote:
> On Feb 1, 8:39 am, Ben Appleton <[email protected]> wrote: > > Very interesting explanation. > > Slightly off-topic but closely related: > > What is the purpose of "&s=Galileo" ? > Barry answers below: this works around hash collisions in Firefox's cache. I don't know if recent versions of Firefox still have this issue. > Have you considered dropping the "cookie" parameter on Satellite tiles > to improve caching across sessions and/or with proxies ? > > http://code.google.com/p/gmaps-api-issues/issues/detail?id=1655 > Yes, we have considered this. > The API V2 & API V3 use different tile name conventions which means > cached tiles cannot be shared among applications running different > versions of the API. > We attempt to keep them in sync, though this matters a little less as v3 traffic grows. I'll take another look. > -- > 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]<google-maps-js-api-v3%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-maps-js-api-v3?hl=en. > > -- 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.
