问题描述
我正在创建一个包含聊天信使的应用.为 Firebase Cloud Message 实现了一个示例.我确实发现消息传递是免费的，所以我很高兴.但现在的问题是它有多可靠?
I'm creating a app having a chat messenger within it. Implemented a sample for Firebase Cloud Message. I did found out that messaging is free, so I'm good to go. But now the question is how reliable is it?
一年前，当 GCM 很简单并且不使用 FCM 时，它并不那么可靠，我们过去常常在收到 GCM 消息时开始调用我们的 api.但是现在，即使我暂时离线，FCM 似乎也会发送所有消息，而当我上线时，它确实会发送.那么它真的是 100% 可靠吗?
A year back when GCM was simple and didn't use FCM it was not that reliable, we used to start calling our apis when we receive a GCM message. But now FCM seems to send all the message even if I'm offline for the moment and when I become online it does deliver. So is it really 100% reliable?
我可以只使用 FCM 进行消息传递，还是应该继续使用旧程序，在收到 FCM 消息时调用我的 api?
Can I just use the FCM for messaging or should I still stick with the old procedure of calling my apis whenever the FCM message is received?
有人测试得这么彻底吗?有什么建议吗?
Any one tested it so thoroughly? Any suggestions?
推荐答案
有人测试得这么彻底吗?有什么建议吗?
Any one tested it so thoroughly? Any suggestions?
现在正在测试它.到目前为止，可靠性看起来并不是 FCM 最强的一面.消息会随机延迟一段时间，有时长达几分钟.有些消息永远不会出现.交付给 iPhone 似乎更可靠，而 Android 则非常不稳定.未交付对我来说实际上是一个阻碍，但 FCM 开发人员似乎并不关心可靠性，这很奇怪:
Testing it right now. So far the reliability doesn't look like the FCM's strongest side. Messages are delayed for random periods, sometime up to minutes. Some messages never show up. Delivery to iPhones seem more reliable, Androids are very erratic. Non-delivery is actually a show stopper for me, but FCM developers don't seem to care about the reliability which is odd:
https://github.com/firebase/quickstart-android/issues/83
https://github.com/firebase/quickstart-android/issues/194
这篇关于Firebase 云消息的可靠性如何?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持跟版网！