In Bluemix push notification, there may be multiple devices subscribe to a tag. When the tag is deleted from the server using REST API, what happens to the devices that are subscribed to the tag? Is there an automatic unsubscribe?
How to do the clean up?
Thanks.
Jen
Short Answer: No clean up is needed.
Long Answer: The subscriptions are maintained by the Push Notifications service Bluemix instance. When a tag is deleted, so is all the information with that tag, including subscribers. There is no automatic unsubscribe because the tag ceases to exist and no further action is needed from the client side.
Related
I searched and found nothing for my question. Is there any special restriction or limitation using Onesignal web push notification? I mean different technologies for front-end and back-end or any special consideration. Or that only depends on browser?
tnx
you can add a new tag for your notification timeout every time user logs in and when sending notifications check this tag with your server current time.
As title I wanna know that does MFP 8.0 support send broadcast event ?
For example : a passenger picked up a trip, he want drivers know about his request. Does MFP 8.0 support simple way to do it ?
Sure. You can use the Push Notifications functionality.
In the MFP console, create a tag called "Broadcast".
In your mobile app's initialization routine, register for that tag (i.e., subscribe to it).
When the business event happens, use the server-side push notification API to send a notification to the tag "Broadcast". This might be an insert to a "Trips" table in your backend database.
All devices that subscribe to that tag will get the notification.
-Paul Horan-
IBM
Let say user A subscribe event source push notification at device A at 10am and subscribe event source push at device B at 11am without unsubscribe. If my backend send the push message, both devices will receive the push message? I actually just want to send the message to the latest devices user have subscribed. Is there anyway to do this?
Like Idan suggested you can inspect push subscriptions in the database . Susbscriptions have an associated timestamp entry . With this you can determine the latest one for the user.
You can then use WL.Server.notifyDevice(userSubscription, device, options) or WL.Server.notifyDeviceSubscription(deviceSubscription, notificationOptions) to target a specific device.
If the user subscribed to two different event sources then yes, the user will receive notifications in both event sources...
There is no built-in mechanism that will prevent "duplicate" subscriptions (of the same user), so perhaps you could implement some sort of a cron job on your server to inspect the subscriptions table in the database and check that there are no duplicate subscriptions. If a duplicate subscription is found, delete the older one.
In the Facebook Analytics document, it said the Push Notification could deep link to a certain page in the app, but I cannot find how to setup the deep link in the "Push Notification" campaign.
Does anyone how to set it up?
Thanks
Facebook Analytics supports two types of push campaign - standard push notifications and in-app notifications.
For standard push notifications, if you want to deep link you'll need to manually configure the push payload by enabling 'Attach JSON Data' (see here for iOS docs on payload). This existing stackoverflow answer explains how to deep-link in push - Deep Linking iOS Push Notifications. Basically you include some meta data that you handle in your app yourself and take the appropriate actions. See screenshot below with productIdToOpen parameter.
For in-app notifications it's even easier. Assuming you've already setup a scheme for your app to handle deep-links from the web, you can just configure one of the buttons to use that scheme. See the screenshot below.
I have developed an android application with the Parse push notification service and I can send notification from the Parse website.
How can I send push notifications through my own website using ASP.net? Is there any way?
I checked the Parse documentation but i get confused, I would really appreciate it if someone would help me.
Thanks
I ran into similar confusion. I wasn't even sure how to properly setup the user so that I could send a push notification directly to them. Then I found the following post:
Channels and Targeted Push Notifications
Note the last item under the Channels heading:
Most apps might find it useful to have a channel for each user so that
they can send messages to a user across all their devices and have
users follow others in the app.
So, now I know that I should subscribe each user to a channel that uniquely identifies the user (e.g., the 'bobsmith#foo.org' channel).
After I have subscribed the user to their channel, I can call Parse's REST API via my ASP.NET application. See Sending Pushes in the Parse REST API Developers Guide.
For an ASP.NET/C# example of how to submit a push notification check out this answer.