C2dM 的缺点
我们都知道,从 Android 2.2 开始,存在推送通知系统(C2dM)。但是,我没有看到很多开发人员使用它。 在我的下一个项目中,我计划(希望如此)使用这个系统。所以在深入研究它之前,我想知道它有哪些不好的方面?为什么人们不使用它?
这不仅仅是因为与 2.2 之前的系统不兼容。
We all know that as of Android 2.2 a push notification system exists (C2dM). However, I do not see many developers using it.
In my next project I plan (hope so) to use this system. So before I dig into it, I would like to know what are the bad sides of it? Why people do not use it?
It can't be just because of incompatibility with systems older that 2.2.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(2)
好问题。这是我的 2 美分:
我不认为人们没有使用它。相反,我发现大多数开发人员对此非常感兴趣并且正在实施它。我的 C2DM 帖子 访问者最多我所有的帖子。
然而,问题可能出在开发独立应用程序的个人开发人员身上。他们可能不愿意使用它,因为他们需要维护服务器端组件来推送消息。
[将更新我的答案。如果我发现任何其他东西。]
Nice question. Here is my 2 cents :
I don't think people are not using it. Rather I find most developers are very much interested in it and are implementing it. My C2DM post has the most visitors of all my posts.
However the problem might be for individual developers who develop stand alone apps. They may be reluctant to use it since they will require to maintain a server side component to push messages.
[Will update my ans. if I find anything else.]
我认为很多人不使用它,因为
使用Apple Push,它非常简单(在设备端),您只需调用一个调用,它就会为您提供设备令牌。使用C2DM,您必须(尽管您可以挖掘Google帐户)提示用户输入Google帐户,然后您必须希望他们没有太多已注册C2DM的应用程序(现在限制100个)。
服务器端,我想说 C2DM 比推送容易得多,您只需调用一个服务,使用 APNS 您需要设置管道、使用证书等。这对大多数人来说并不容易做到。 C2DM 只是调用 HTTP 调用。服务器方面也增加了一些费用,托管应用程序服务并不总是便宜。
我没有看到很多应用程序需要它,到目前为止 Twitter 和 Facebook 似乎需要它(尽管他们可能使用其他东西,我不确定)。
而且,它仍然是测试版服务。开发人员是否愿意在测试版服务上投入大量时间?并非所有人都这样做,有些人会冒险。
我已经使用过它并且喜欢它,我将它与 APNS 结合起来,到目前为止已经取得了巨大的成功。
I think a lot don't use it because
With Apple Push, it is pretty straight forward (on the device side), you simply invoke a call and it gives you the device token. With C2DM, you have to (though you can dig for the google account) prompt the user for the google account, then you have to hope they don't have too many Apps already registered for C2DM (100 limit now).
Server side, I'd say C2DM is a lot easier than push, you simply are invoking a service, with APNS you need to setup pipes, use certificates, etc. It isn't easy for most to do. C2DM is just invoking a HTTP call. The server aspect adds a bit of expense as well, hosting application services isn't always cheap.
I don't see a lot of Apps having the need for it, so far Twitter and Facebook seem to be (Though they may be using something else, I am not sure).
And, it is still a beta service. Do developers want to invest a lot of time in a beta service? Not all do, some will take the risks.
I've used it and I like it, I have it coupled with APNS and have had great success so far.