C2DM可靠性 [英] Reliability of C2DM

问题描述

我有C2DM问题。有时候完美的作品，有时候我的消息根本没有得到推动。 有没有可靠的方法来执行这个连接？要提取消息。我读的地方，就是谷歌要做的就是继续在所有的时间低带宽的TCP连接到他们的服务器。所以，我认为 网络类型之间切换时，TCP连接摔倒和Android试图重新建立连接C2DM服务器。所以这可能与受限制的网络故障的无线网络。 是错误的假设？

I am having issues with C2DM. Sometimes works perfectly, sometimes my messages simply do not get pushed. Is there reliable way to enforce this connection? To pull messages. I read somewhere that what google do is keep low bandwidth TCP connection to their server at all time. So I assume that when switching between network types TCP connection falls down and Android tries to reestablish connection to C2DM servers. So that might fail on WiFi with restricted network. Is that wrong assumption?

我注意到与WhatsApp的上的WiFi有时我没有得到消息。当我切换到3G，我通常让他们在开关的一刻。 会为您提供什么秘诀，从与C2DM的心得？

I have noticed with WhatsApp that on WiFi sometimes I do not get messages. When I switch to 3G I usually get them at the moment of the switch. What tips from your experience with C2DM would you offer?

推荐答案

C2DM是不适合你的应用程序的关键部分，因为谷歌目前不提供SLA或支付的层次，将保证您可靠的服务和吞吐量。

C2DM is not suitable for critical parts of your application, since Google currently does not offer an SLA or paid tiers that will guarantee you reliable service and throughput.

我已经考虑了几种选择自己： XMPP通过asmack ，的解析，执事，<一个HREF =htt​​p://urbanairship.com/相对=nofollow>城市飞艇和 MQTT 。

I've considered several alternatives myself: XMPP via asmack, Parse, Deacon, Urban Airship, and MQTT.

在一些阅读和试验，我决定去与MQTT。它发明了IBM的非常轻便遥测协议，很好地适合在Android推送通知的情况。我建议你​​给它一个尝试，这里是一个不错的博客文章来引导你：在Android手机使用MQTT 应用的。

After some reading and experimenting I decided to go with MQTT. It is a very lightweight telemetry protocol invented at IBM that fits quite nicely in the Android push notifications scenario. I recommend you give it a try, here's a nice blog post to guide you: Using MQTT in Android mobile applications.

希望这有助于。

这篇关于C2DM可靠性的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！