将应用服务器从GCM迁移到FCM时,旧客户端会发生什么情况? [英] What happens to older clients when you migrate an app server from GCM to FCM?

查看:187
本文介绍了将应用服务器从GCM迁移到FCM时,旧客户端会发生什么情况?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我正在考虑迁移到FCM。事情的客户端很简单,你移动一些代码并完成它。但是,在应用程序服务器上,出于显而易见的原因,我还需要支持较老的客户端。我需要知道将GCM项目迁移到FCM时会发生什么。 FCM是否会自动将消息转发给较早的基于GCM的客户端?或者我需要将每条消息发送两次,一次发送给FCM,一次发送给GCM?这将如何影响特定于实施的内容,例如从Firebase的Web控制台发送的消息?是否有任何细节我应该知道?

解决方案

使用FCM(导入的项目或使用它的端点,无论你的意思)仍然与GCM客户端(特别是令牌)兼容。他们仍然可以像往常一样接收消息。



看到这些类似的帖子:

>

I'm considering migration to FCM. The client side of things is rather simple, you move some code around and get it done. However, on the app server, I'd need to support older clients as well, for obvious reasons. I need to know what happens when I migrate a GCM project to FCM. Does FCM automatically forward messages to older GCM-based clients as well? Or would I need to send each message twice, once to FCM and once to GCM? How will this impact implementation-specific stuff such as messages sent from Firebase's web console? Are there any details I should be aware of?

解决方案

Using FCM (an imported project or using it's endpoint, whichever you mean) is still compatible with GCM clients (specifically tokens). They'd still be able to receive messages like usual.

See these similar posts:

这篇关于将应用服务器从GCM迁移到FCM时,旧客户端会发生什么情况?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆