Generate your key and create a file named domain.js. Put the key in there instead of mainline in your code. So when you upload new code pages, the key isn't embedded in that code. And you can keep track of what key is for what domain by the filename.
Of course with thousands of domains, it seems like stuffing that in a database table so it can be selected on the fly (again driven off the domain name) would be sensible if they all can access one common data table. On Oct 30, 6:36 pm, helloworld <[EMAIL PROTECTED]> wrote: > Damn you'r amazing! It seems what you have a solution for > everything :) > The overwriting is exactly what i need! Shame on me for don't think of > it! > I'll check for GBrowserIsCompatible() just for see, but my problem is > solved anyway. > Thanks again! --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
