I know am responding to a very old thread. But, this is also a matter of
optimization. If you are developing a Progressive web app, all your
resources are cached(js, css and images) in the browser. But, google maps
js files needs to be loaded from google server. No mater what you do to
improve
Hey, thanks for all the feedback; it sounds like this is a no go.
The reason why is just to be as little dependent on a third party
server as possible. Since a web page already has a connection to our
server I've noticed a jump in time when it makes a separate connection
to the google.com servers.
We don't mind if you cache the bootstrap code for no more than 30 minutes at
a time (that is the public caching policy for that file), otherwise we do
not guarantee that the API will work correctly. So in other words, your
server will need to get a new copy every 30 minutes :)
If you plan to suppo
As said above, this is a violation of the terms & services.
But also, *why*? Unless you're using custom tiles, you're relying on us to
provide you with tiles and other services anyway.
We have spent a lot of time tweaking performance to ensure that the
JavaScript loads in a way that provides the
On 20 October 2010 22:41, dmcewan wrote:
> That's not really the solution I was hoping for as I am hoping to remove the
> dependency on the google servers for javascript load entirely.
You can't remove the dependency because you must use the documented
call to the API script in order to stay with
That's not really the solution I was hoping for as I am hoping to
remove the dependency on the google servers for javascript load
entirely.
Thank for the reply though.
--
You received this message because you are subscribed to the Google Groups
"Google Maps JavaScript API v3" group.
To post to
