Question

我的推送通知适用于我的移动Android应用通过GCM，但有一个关于我的环境的具体问题。我的应用程序希望能够接收超过100的推送文件中的发件人（服务器）和评论（见下文）让我感到困惑。

基本上考虑这种情况......

我在Google Dev Console上注册了我的项目并获得了我的项目项目编号（aka - 发件人ID）和我的服务器密钥。对于后者我没有指定特定的IP地址..只是将字段留空了。
我的应用程序启动并使用此单个发件人ID进行“注册” 并收到注册码。
我将此注册密钥发送到我的500“源”服务器，以及这些服务器拥有SAME服务器密钥。

再次总结一下......我想要发送推送到手机的500台服务器 ALL使用SAME服务器密钥和SAME注册ID。

简单的问题..这是允许的吗？如果是这样，所有限制警告意味着什么（下面）来自GCM文档....如果不允许，我想在技术上理解为什么不允许这样做..例如，GCM服务器是否监控并保留跟踪服务器密钥及其来源IP？

非常感谢 - 一直在寻找日子并且无法得到真正的答案我觉得我可以信任。我的整个开发项目设计取决于真相这件事 - 哈哈！

从多个发件人接收邮件

   "GCM allows multiple parties to send messages to the same application. For example, 
    suppose your application is an articles aggregator with multiple contributors, and 
    you want each of them to be able to send a message when they publish a new article. 
    This message might contain a URL so that the application can download the article. 
    Instead of having to centralize all sending activity in one location, GCM gives you 
    the ability to let each of these contributors send its own messages.

    To make this possible, all you need to do is have each sender generate its own project 
    number. Then include those IDs in the sender field, separated by commas, when requesting 
    a registration. Finally, share the registration token with your partners, and they'll 
    be able to send messages to your application using their own authentication keys.

    Note that there is limit of 100 multiple senders."

或在其他一些文档中用另一种方式表达......

从多发件人接收邮件

   "GCM allows multiple parties to send messages to the same client app. For example, 
    suppose the client app is an articles aggregator with multiple contributors, and 
    each of them should be able to send a message when they publish a new article. This 
    message might contain a URL so that the client app can download the article. Instead 
    of having to centralize all sending activity in one location, GCM gives you the ability 
    to let each of these contributors send its own messages.

    To make this possible, make sure each sender generates its own sender ID. See the 
    client documentation for your platform for information on on how to obtain the GCM 
    sender ID. When requesting registration, the client app fetches the token multiple 
    times, each time with a different sender ID in audience field.

    Finally, share the registration token with the corresponding app servers (to 
    complete the GCM registration client/server handshake), and they'll be able to 
    send messages to the client app using their own authentication keys.

    Note that there is limit of 100 multiple senders."

甚至在我看到的一些注册码中......

    chrome.runtime.onStartup.addListener(function() {
      chrome.storage.local.get("registered", function(result) {
        // If already registered, bail out.
        if (result["registered"])
          return;

        // Up to 100 senders are allowed.
        var senderIds = ["Your-Sender-ID"];
        chrome.gcm.register(senderIds, registerCallback);
      });
    });

GCM推送发件人/服务器限制为100

0 个答案: