It's almost certainly impossible to protect your data from an attacker with sufficient skills, but you can make life difficult for them by encrypting your data.
Here's a really simple example: The data http://econym.org.uk/temp/encoded.txt The page that uses it http://econym.org.uk/temp/decodeXML.htm In this case it would be quite easy for someone to read the source of decodeXML.htm and work out how to decipher it, and it's a really simple Caesar cypher anyway. But even if you use a powerful cypher, write a complicated decoding function and obfuscate your code, someone could just take a copy of your decode function. You can't store your encoded data in a .XML file unless your cypher happens to preserve XML-ness. My example fails that because the < and > are encoded as μ and &hu; which are invalid entities. I suspect that you may have to arrange that your cypher text contains only ASCII characters. That's not too difficult. In the worst case you could encode to non-ASCII and then convert that to a string of digits that represent each character. -- 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 -~----------~----~----~----~------~----~------~--~---
