This issue comes and goes in this thread all the the time. I also suggested in the past to delegate the job to the client since I could't see a scenario where we use server side request and be within the TOR's. (see here : http://gaengine.blogspot.com/2010/05/google-maps-api-quotas-and-app-engine.html ) I was wrong. Recently I run into a case where I had to do this and still I am sure I am within legal limits, this is so when you need the geolocation service in order to publish a static map served from Google. So this is a real problem and the issue has to be resolved somehow, although I think we are discussing this in the wrong group. IMO that this is an issue for the maps group and we should adress it there.
Happy coding:-) On Jul 8, 10:29 pm, Zarko <[email protected]> wrote: > Yes, it is in use with a Google map, actually I am trying to save > requests to Google from clients... > > On Jul 8, 6:43 pm, Barry Hunter <[email protected]> wrote: > > > > > On 8 July 2010 16:08, Zarko <[email protected]> wrote: > > > > By the way I can't transfer the job to the client (it's not a browser > > > app). > > > Are you sure your app is using the API legally then? > > > *Note: **the Geocoding API may only be used in conjunction with a Google > > map; geocoding results without displaying them on a map is prohibited.* > > * > > * > > fromhttp://code.google.com/apis/maps/documentation/geocoding/ -- You received this message because you are subscribed to the Google Groups "Google App Engine" 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-appengine?hl=en.
