MapView api 密钥和应用程序指纹
我想建立一个 Android 架构，类似于 google 允许使用 api 密钥访问其地图的方式。
我不确定的是，应用程序的指纹是否会在每次检索地图图块的请求时与 api 密钥一起发送，或者 api 密钥是否只是在每次请求时单独发送？
如果指纹确实与 api 密钥一起发送，那么应用程序如何以编程方式获取自己的指纹？
谢谢， 多姆
I'd like to set up an android architecture similar to how google allows access to their maps using an api key.
Something I'm unsure about is if the fingerprint of the app is sent up, along with api key, on every request to retrieve a map tile - or is the api key just sent up on its own on each request?
If the fingerprint is indeed sent along with the api key, then how does the app programatically get its own fingerprint?
Thanks,
Dom
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
那么基本上您希望您的用户生成自己的 API 密钥并将其用于对您的服务的每个请求？
唯一有意义的情况是您想跟踪谁做了什么。在这种情况下，您需要在用户提出的每个请求中发送 API 密钥（基本上就是您的指纹）。
Google 使用 API 密钥来识别谁使用其服务执行什么操作。这对他们来说很有意义，因为他们靠收集数据为生。
我对此的看法是：如果您想提供开发人员应该用来为其应用程序提供一些新功能的服务，那么它不应该需要 API 密钥。人们会发现这更烦人而不是有用。除非你有充分的理由需要跟踪他们的行为......
So basically what you want is your users to generate their own API-Key and use it for every request to your Service?
The only scenario in which this would make sense is if you want to keep track of who does what. In this case, you'll want to send the API-Key (which basically is your fingerprint) with every request your user makes.
Google uses the API-Key to identify who does what with their service. This makes sense for them since they life from collecting data.
My opinion on this is: If you want to offer a service that developers should use to give their apps some new functionality, it shouldn't need a API-Key. People will find that more annoying then useful. Unless you have a very good reason why you need to keep track of their actions...