Thanks guys! My concern is with two distinct cases where the key installed on the site needs to be tested:
1) Immediately after initial installation. This is because we generate keys and install them automatically, in batches, and they need to be QA'd. 2) For the case where we've regenerated an existing site's key in the automated batch process. I was hoping GoogIe had a separate API for testing. I will look into the javascript solution. It's a little more hands-on than I prefer, but a good idea nonetheless. On Nov 25, 6:41 am, Mike Williams <[EMAIL PROTECTED]> wrote: > Wasn't it ProbablyMike who wrote: > > >Only way I can think of for a key to become invalid is for the URL/ > >Domain name of the website to change. > > If you're doing something that Google really don't like, then Google > might well be able to block your key. > > Also, there was a situation not long ago where the introduction of a > server side key validation routine caused some sites to fail validation. > > As regards automated testing, it should be possible to write a master > page that contains an <iframe>. Use Javascript to change the "src" of > the <iframe> every few seconds to cycle through all the sites. Leave it > running while you go do something else. If one of the API keys fail, > then the resulting alert will pause the cycle. > > --http://econym.org.uk/gmap > The Blackpool Community Church Javascript Team --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
