Andrew, I have an idea and suspect that its possibly a legitate rather than sneaky way around.
On my default.aspx page the site landing page I have a LOT of white space. The company MD asked if I could put our company name, address and contact details on here. If I were to include a map too that would then ensure ALL site visitors have access to Google Map and justify the Api code? Would I be correct in assuming this? PS It still doesn't solve my IE problem! Anyone come across this, see original post and note I do not care about the warning about secure and non secure. I accept my my data will be unsecure and that isn't an issue for me. On Dec 31, 7:03 pm, milesba <[email protected]> wrote: > This happens to be my challenge as well. We have built an operational > dashboard using the free Gmaps API. The markers are called dynamicaly > based on the state of our fuel sensors at the given locations. > According to the Google maps API TOS, the map must be publicly > accessible. The problem is that a compettitor of my client can see > (according to the TOC) the state of the sensors at any given time. > This seriously compromises our business model, not to mention SLA's > and confidentiality agreements with our prospective clients. I have no > problem buying a premier license and securing the whole map, but since > this is a prototype application, I cant justify paying the $10K before > I know that I've got a winner. I will explore the cookie method for > now, but if Google wants to totally dominate dev API environments, > they should possibly consider a new licsence type for development of > proprietary but prototype application without the need for massive > capital outlay. > > On Dec 31, 8:21 am, Andrew Leach <[email protected]> > wrote: > > > On Dec 31, 3:11 pm, SteveCurrie <[email protected]> > > wrote: > > > > Correction to the above post we will never charge for this service. > > > But you *are* restricting access to your map? That falls foul of 9.1. > > You can require users to log in to your application providing that > > logins are freely available to anyone who asks for one -- whether or > > not they are your staff, your customer or your competitor. > > > One way round this is to make the *map* publicly accessible, but only > > show your *data* on that map if you can identify the user (eg via a > > cookie set on logging in). You can use the cookie server-side to > > determine whether the "get data" Javascript is delivered to the > > browser so an anonymous user has no idea there is anything else. > > > Andrew -- 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.
