has nothing to do with secrets dude, i dont want to spend hours building map content for someone else: I obviously want to share___ I just dont want YOU, THEM, Whoever to download my work without my permission.
if you'll actually read the message you'll see that while i dont completely understand how google sends the kml to my map (as i am not a programmer, etc...) - i do get that they need accees and thats what i'm trying to figure out so I can publish my maps but protect my physical data i've built: if you want to be snippy - please don't bother replying i need help not meaningless commentary. On Oct 20, 2:51 pm, Rossko <[email protected]> wrote: > > Using s3 storage, I can load google maps v3 (not from s3 but from my > > website), i cannot download kml directly from s3 (which i want to > > protect my actual kml files from being downloaded) > > > BUT - google maps v3 won't load the kml file using the enclosed s3 > > Bucket Policy, but will load the kml using public read ACL. > > I've no idea what all that means. > But my guess is that you have overlooked that the KmlLayer client > doesn't access your KML at all ; it passes the URL to Google's > servers, they read your KML source and render it at Google's end, > passing overlay tiles back to the client. > If you want to display KML it needs to be public. > If you want to keep secrets, don't put it on a webpage at all. -- 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.
