In my experience, a recurring concern about push notifications is sending notifications to a particular user of your service.
To achieve that, you have to maintain the matching between user id and its push notification tokens.
So, to achieve that, I would need :
a microservice to maintain the user id/push token matching
an instance of GoRush to actually send the notifications
It would be really convenient to add that responsability to GoRush.
Hi @appleboy ,
here is a thought I would like to discuss...
In my experience, a recurring concern about push notifications is sending notifications to a particular user of your service. To achieve that, you have to maintain the matching between user id and its push notification tokens.
So, to achieve that, I would need :
It would be really convenient to add that responsability to GoRush.
New API proposal
POST /api/session
POST /api/push/session
Cleaning the mapping
In case of invalid tokens (expired, invalid...) we want to remove it from the session mapping.
Fortunately, when sending notifications with services like Firebase Cloud Messaging, it returns the list of invalid tokens used.
What do you think ?