> has nothing to do with secrets dude, i dont want to spend hours > building map content for someone else:
Okeydoke, but if you show people your content you can't stop them stealing it - with more or less work needed. You can only make it difficult. > if you'll actually read the message you'll see that while i dont > completely understand how google sends the kml to my map Hopefully, you do now. What you need to know is the IP address of the Google server that reads the KML source. You can't get that from monitoring activity at the client, you'd need to look at server logs. I can't tell it to you because... The big problem is that it might be different every time - as Google resources are 'cloudy'. If you did manage to find a _range_ of addresses, it might still all change without notice next week. Make the range too inclusive and you have no security and the whole thing becomes pointless. The worst is that you wouldn't know when Google changes unless you check the map yourself regularly, users would just see the empty map with no error message, like your present test case. As an alternative suggestion, you could render your data at your own server as map tile images. It's a lot more work, but about as difficult as you can make it for data scrapers - the actual data never leaves your server, only images. Of course you might then need to look into mechanisms to discourage image tile scraping (like Google do)... -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" 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-js-api-v3?hl=en.
