On Oct 16, 2:01 pm, RW <[EMAIL PROTECTED]> wrote: > Transfering the work to the client would indeed be the most logical > solution. However, the clients are phones, some first tests we did > some months ago indicated that not all phones retrieved an image when > the request was not directly to a url of an image > (http://...something.jpg) but tohttp://...php?something. > Therefore we build the server component to retrieve the image, after > which the mobile requests it, unchanged, from the server component.
So you're effectively building a proxy server which intercepts requests for ".jpg" files and constructs an image to transmit. Provided that NO changes are made to the image Google provides, it's *probably* within the TOU [but I'm not a lawyer and this isn't a clear- cut example]. You might consider use of the X-Forwarded-For HTTP request header (using the IP address of the client device), but I've no idea whether Google uses that header to determine the IP address it counts. It may use that in association with a whitelist of known proxies. Note that if the client device also connects via a proxy [Orange mobile phones do] then there may already be such a header which you need to honour when transmitting onward to Google. 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 -~----------~----~----~----~------~----~------~--~---
