混乱迁移Parse推送到AWS SNS [英] Confusion migrating Parse push to AWS SNS

问题描述

如最近的aws博客帖子及其后果:

不得不依靠我的所有用户及时更新似乎很麻烦，以便可以将GCMSenderID与经过修改/有效的设备令牌一起附加到我现有的解析数据中.

It seems like quite a bit of trouble to have to rely on all my users to update in a timely fashion so that GCMSenderIDs can be attached to my existing parse data along with modified/valid device tokens.

此外，迁移完成后新安装将如何处理?在指南中，它说不需要对客户端代码进行任何更改，但这是否不要求安装SNS sdk以便可以将新安装内容添加到客户端列表中?

Also, what happens to new installations after the migration is complete? In the guide it says no changes need to be made to client side code, but doesn't this require that the SNS sdk is installed so that new installations can be added to the client list?

考虑到所有这些，简单地忘记旧的解析数据，然后推送仅适用于SNS的客户端/应用程序更新并以这种方式重新注册所有设备，是否更有意义?无论如何，为什么要摆脱与Parse集成的所有麻烦呢?

Considering all this, wouldn't it make a lot more sense to simply forget about the old parse data and just push a client/app update that works solely with SNS and reregister all the devices that way? Why go through all the trouble to integrate with Parse when we are getting rid of it anyways?

推荐答案

AllTheTime，

AllTheTime,

由于Parse拥有与被授予令牌的发件人ID关联的API服务器密钥，因此您在Parse.com上现有的Android用户推送令牌将在2017年1月28日之后失效.希望在一月份后通过推送通知"吸引这些现有用户，则必须使用您自己的发件人ID更新现有的Parse.com客户端应用，并让该应用生成与您的发件人ID相关联的新注册ID(令牌).没有其他方法可以将现有令牌转换为SNS或任何其他第三方.

Your existing Android user push tokens on Parse.com will no longer be valid after January 28, 2017 as Parse owns the API Server Key associated with the Sender ID that was granted the token. If you wish to reach those existing users via Push Notifications after January, you must update the existing Parse.com client app with your own Sender ID and have the app generate a new registration Id (token) associated with your Sender ID. There is no other way for you to convert the existing tokens over to SNS or any another 3rd party.

迁移不需要SNS SDK，但在更新应用程序以使用发件人ID检索新令牌时，将SNS SDK集成起来是有意义的.在令牌注册时，应用程序可以使用新发行的令牌更新Parse.com数据库，还可以使用SNS创建新的Platform Endpoint.

The SNS SDK is not required for the migration but it would make sense to integrate the SNS SDK when you update the app to retrieve new tokens using your Sender ID. At the time of token registration, the app can update the Parse.com database with the newly issued token AND also create a new Platform Endpoint with SNS.

对于后Parse Push迁移和处理新应用程序的安装，我的建议是在Parse.com上的_Installation类上构建一个保存后的"webhook".在_Installation类中创建或更新行时，"webhook"将触发任何http端点.该挂钩可能会触发API网关http端点，该端点采用新生成或更新的令牌并创建新的SNS平台端点.此时，如果您尚未完全从Parse.com迁移，则可以通过Parse.com或SNS发布到这些令牌.到2017年1月28日到来的时候，几乎所有现有用户都将启动更新的应用程序并生成一个新令牌，否则他们将不再使用您的应用程序.

As for post Parse Push migration and handling the new app installations, my suggestion is to build an after-save "webhook" on the _Installation class on Parse.com. The "webhook" would trigger any http endpoint when a row is created or updated in the _Installation class. The hook could trigger an API Gateway http endpoint that takes the newly generated or updated token and creates a new SNS platform endpoint. At this point, if you haven’t fully migrated from Parse.com, you can either publish to those tokens via Parse.com or SNS. By the time Jan 28, 2017 rolls around, nearly all your existing users would have launched the updated app and generated a new token or they no longer use your app.

仅从SNS重新开始是另一种选择，但是如果您需要吸引尚未更新应用程序的任何用户，则需要继续通过Parse.com发送这些旧版的推送通知用户尚未更新应用，然后您将继续通过SNS向这些新应用安装发送推送通知.

Starting over with just SNS is another option but if you need to reach any of the users who have not updated the app then you would need to continue sending push notifications through Parse.com for those legacy users who have not updated the app AND you would then continue to send push notifications via SNS to those new app installs.

我希望这可以为您澄清迁移过程.

I hope this clarifies the migration for you.

查看我有关Parse.com GCM发件人ID的其他SO帖子: 如何从Parse迁移到其他SENDER_ID

Check out my other SO post regarding the Parse.com GCM Sender ID: How to migrate off Parse to different SENDER_ID

-丹尼斯

这篇关于混乱迁移Parse推送到AWS SNS的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！