GCM API密钥与发件人ID [英] GCM API key vs Sender ID

问题描述

我对GCM发件人ID和API密钥感到困惑。我负责构建将向Android应用发送通知的第三方服务器。

我必须在服务器端存储哪一个？ API密钥或发件人ID？谁负责创建Android开发人员或我？负责创建这两​​个开发人员或我？

p>

1. API密钥在控制台上生成，并由第三方服务器用于使用GCM进行身份验证/授权。


2. 发件人ID由Android应用程序使用GCM注册物理设备，以便能够从特定第三方服务器的GCM接收通知。


3. 注册ID是注册物理设备的结果使用发件人ID到GCM。

I am confused about GCM Sender ID and API key. I'm responsible for building 3rd party server that will send notifications to Android app.

Which one do I have to store on server side? API key or Sender ID? Who is responsible for creating both, Android developer or me?

解决方案

I've kinda figured it out on my own:

1. API key is generated on console and is used by 3rd party server to authenticate/authorize with GCM.
2. Sender ID is used by Android app to register a physical device with GCM to be able to receive notifications from GCM from particular 3rd party server.
3. Registration ID is a result of registration of physical device to GCM with Sender ID.

这篇关于GCM API密钥与发件人ID的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！