This should do the trick. The Application does not plot all 17k results at a time, We are in the process of selling, but they want to see the thing work in practice. So, after they paid me, I don't care if they do that. It is just for the trail run I want to protect the data for now.
On May 10, 11:30 pm, Andrew Leach <[email protected]> wrote: > On 10 May 2011 21:36, Jaques Burger <[email protected]> wrote: > > > Hi there. > > > Is there any HTTPS support on the Elevation API yet? My app is uing > > Lat's and Longs that is encrypted in the database, and I don't want > > the users to use something like wireshark to catch the packets and get > > the information anyway. They have to pay for the data that I provide, > > and the moment they have that information, they don't need me anymor. > > In most cases it's the app itself at the end of the journey which is > the most vulnerable point, rather than traversing the network, > considering that the elevation results must be displayed on a Google > map (which in turn is likely to mean a browser or browser control). > > A url like that specified in the docs seems to work, but I can't vouch > for its security credentials. I assume it's > encrypted.http://code.google.com/apis/maps/documentation/javascript/basics.html... > > https://maps-api-ssl.google.com/maps/api/elevation/xml?locations=51,0... -- You received this message because you are subscribed to the Google Groups "Google Maps API V2" 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.
