On 23/07/2009, Pil (Trustworthy from Experience) <[email protected]> wrote: > > If the industry regulations may distrust Javascript files that are > loaded directly from a Google server then they may also distrust > Javascript files that came from Google and are now hosted on their own > server. > > I can see no difference here.
I guess the difference is they can 'vet' the copy they take at that time, and know that its not going to change. But that doesnt change that the API always needs to load scripts of other servers (eg the copyright string loading) - so even if could take a copy of the main scripts - it would further break the terms by breaking the branding links. Maybe the client could invest in the Permeier version - which may well come with additional SLA agreements. > > > > > > On Jul 23, 6:07 pm, ecornips <[email protected]> wrote: > > > Hi, > > > > Is it possible (from a legal/licence/terms of service) point of view > > > to host the maps javascript files yourself, so you don't refer to > > e.g.http://maps.google.com/maps?file=api&v=2&key=abcdefg.... but > > insteadhttp://www.example.com/js/maps.js? > > > > > The main reason I ask is a customer is not allowed to reference > > javascript outside their own domain, as it's a security risk. While I > > may trust Google, the customer is bound by industry regulations that > > won't let them reference the file directly from Google. > > > > Thanks, > > > > Mike > > > -- Barry - www.nearby.org.uk - www.geograph.org.uk - --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Maps API" 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-API?hl=en -~----------~----~----~----~------~----~------~--~---
