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 to http://...php?something. Therefore we build the server component to retrieve the image, after which the mobile requests it, unchanged, from the server component.
On Oct 16, 11:23 am, "warden [Andrew Leach - Maps API Guru]" <[EMAIL PROTECTED]> wrote: > On Oct 16, 7:42 am, RW <[EMAIL PROTECTED]> wrote: > > > Our service uses theStaticMap API via a server component. This > > implies a lot of viewers using the same IP address. This seems to be > > the reason why the limit is hit (1000 requests per day per IP?). > > > I try to get in touch with Google to increase the limit but can > > nowhere find a working contact mail address. Anyone a suggestion? > > My suggestion is to transfer the work to the client. I can't see any > benefit in gettingStaticMaps on a server, and at least one > significant disbenefit, which you've found. Why is it necessary to do > it server-side? > > 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 -~----------~----~----~----~------~----~------~--~---
