推送通知延迟与GCM [英] Push notifications delay with GCM

问题描述

我们有一个应用程序（Ruby on Rails）将推送通知发送到Android应用程序，并且我们面临着GCM中的一些问题，其中一些通知延迟或从未收到。考虑到这些通知是发送给员工而不是最终用户的事实，我的问题是：

发送这些推送通知没有任何延迟或丢失的最佳方式是什么有没有办法独立于GCM和SNS等可用服务发送推送通知？

请注意，我们正在寻找一种解决方案，可以发送这些通知必须在发送完成后1到20秒内收到。

预先感谢任何人回答这个问题...

解决方案

查看 Pushy ：

他们在网站上声明如下：

$ b

最可靠的推送通知网关，非常适用于实时
应用程序。

Google科陆电子d消息传递根本不会削减时间敏感的
实时应用程序，因为它的不稳定性和推送通知
限制。

Pushy通过使用MQTT协议来维护专用的后台套接字连接
，这是一种极轻量级的pub / sub协议
，它消耗的网络带宽和电池很少，这使得
非常适合移动设备。

您可以免费使用最多100个设备，所以您可以试试看，如果它适合您的需求。我没有尝试过。

We have an app (Ruby on Rails) that sends push notifications to an android app and we're facing an issue with GCM where some of these notifications are either delayed or never received. Considering the fact that these notifications are being sent to employees and not end-users my questions is:

What the best way to send these push notifications without any delay or drop and is there a way to send push notifications independently from the available services such as GCM and SNS?

Please keep in mind that we're looking for a solutions that can send these notifications without any delay as for the app to perform well the notification must be received within 1 to 20 seconds from the time it was sent.

Thanks in advance for anyone that will reply to this question...

解决方案

Have a look at "Pushy":

They state the following on their website:

The most reliable push notification gateway, perfect for real-time applications.

Google Cloud Messaging simply doesn't cut it for time-sensitive, real-time apps, due to its instability and push notification throttling.

Pushy works by maintaining a dedicated background socket connection using the MQTT protocol, an extremely light-weight pub/sub protocol that consumes very little network bandwidth and battery, which makes it perfect for mobile.

You can use it for free with up to 100 devices, so you could just give it a try to see, if it fits your needs. I didn't try it.

这篇关于推送通知延迟与GCM的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！