I've implemented muc light on mongooseIM chat server and can say good job to the team as this is exactly what we all wanted in mobiles world of group messaging.
1) Have anyone handled the push notification using this much light. As I have used the mod_zeropush for the single chat can I modify the same for supporting mod muc light as well.
2) Also how to handle mam on client side for the offline message as I understand from docs mod_offline can be used only for single chat and not muc light.
Thanks for any guidance given in advance.
I modified the mod_zero push erl and compiled to support the muc chat light message notifications to send to user.
Also when the user wakes up and he gets the next message from the MUC light I fetch the group info to create the group and link rest messages (hence onwards) to this group.
For the previous messages I used the MAM directions as given in this reference link for fetching the archived message from the server. Provided the server is enabled for muc_light message archive.
Related
I am using FCM Cloud Messaging framework to send and receive push messages for both Android and ios. To send messages from my server I call FCM v1 API. I use FCM SDK app in my native app (react native based) to generate device registration token, etc.
I am trying to find ways where the push messages show grouped in device system tray like on Whatsapp i.e. messages containing a particular unique id should be grouped under one category e.g. all messages for a particular stock ticker showing under one group, etc.
When searching for possible solutions I came across various links such as:
React Native - Android - FCM - Display group notification like What's app also allowing multiple grouped notifications
Group fcm notifications like whatsapp but allowing multiple group notifications
But none of those helped. For example sending "tag" field replaces previous message when new one is received with the same value. Moreover when app is closed none of the message handling functions of native app are executing on the device so I believe this should be purely a server side functionality. On FCM docs page there is no reference to grouping of messages.
https://firebase.google.com/docs/reference/fcm/rest/v1/projects.messages
Any suggestions on how to implement this ?
I implemented that with the help of the library react-native-push-notification and this issue helped me a lot Group notifications
I have 2 questions:
1) I need to send HTML in Push Notification IBM MobileFirst as a message, can I achieve it? If yes, how?
2) Using MobileFirst Console, can we send Push Notification? or in case we don't have any adapter/ or data source can we acheive push notification?
glad hearing you guys soon.
Push notifications are meant for very short text-based messages and are limited in size; sending mark-up will in all likelihood exceed this.
In order to use push notifications in IBM MobileFirst, you must use adapters. Please see the user documentation and developer center for more information.
I'm currently in the early stages of designing a cross-platform mobile app (iOS, Android, WP8). At its core, the application will allow proximity based interaction between an unknown number of client devices.
Could someone recommend a framework or technology that would allow me to push server generated location based proximity alerts to the clients that even scales well? Could push notifications (cross platform using PushSharp) be a viable option for this, or will Push notifications always go hand in hand with some kind of toast notification on the device?
Update: 30 seconds or even a minute delay should do.
Push Notifications have way to much latency to give you anything near real-time. Also Push Notifications are not guaranteed to reach a device.
You really need to think about how much time constrained the location updates should be. You should also make some tests with how fast the GPS on various devices updates. I have tested on a Nexus 4 and it is not near real-time either. So throughout your entire application whether it is server side or client side you will have things blowing your real-time wishes.
However IF you can live with a delay of a couple of seconds to maybe 30 seconds or more, Push Notifications my work well for you, they also scales quite nicely.
EDIT:
Push notifications always go hand in hand with some kind of toast
notification on the device?
There is a concept called RAW notifications, which allow you to send arbitrary information with the Notifications. However personally I would just notify the client about updates ready on a server, where it then can get all the information the application needs. This is because as I said Push Notifications are not guaranteed to ever reach the device, but also because you are limited to how much information you can embed in the Notifications.
So my suggestion for a flow would be:
Client A updates its location and sends it to a web service
Web Service receives info from Client A and prepares notifications for all the other Clients, which need information about Client A and pushes information about they need to update their info.
Client B receives a Push Notification telling it to refresh data from the Web Service and does that.
That would work well if the application is in a background state. When showing in the foreground I would simply poll a server every second or so; Still receiving Notifications just forcing the client to update.
For the "scales well" part, you might also want to take a look at Windows Azure Service Bus Notification Hubs. It's currently in preview and supports only Windows 8 Store apps and iOS but support for Android and Windows Phone is on the way.
I heard that there are applications that allow people to do transactions by just touching there iPhones to each other. How is that archive via code in Objective C?
I beleive each phone has to detect the "bump" (using UIAccelermeter) and send an immediate notification of the event ot a server (perhaps with a timestamp and some geolocation info too?). Then the server matches up events that occur at the same moment, to determine the two devices involved. Then the server facilitates the transaction by sending each phone's info to the other.
take a look at the Bump API http://bu.mp/api.html as used in the Bump iPhone application. I haven't used it myself so I cannot say how easy it is to integrate but they claim it only requires you to add ten lines of code.
The way I would do it would be to have each device send the other their UID over bluetooth and then have them both send a message containing the other devices UID and their own UID to the server with a timestamp, then have the server handle the transaction.
i want to know how do i enable my application to use push notification service.i read the guide but doesn't find it much detailed information about it.Could someone tell me an easy way that how it works,what are the requirements,how do i apply this in my app. one thing i would like to know that according to guide the connection between provider and APNs must be asynchronous,What does it mean? also i read that if we continuously connect and disconnect APNs will block the IP. so what is the minimum time difference to connect to APNs after disconnecting.Please guide me in according to the question.thanks
First off, there are quite a few tutorials out on the net for how to do this.
But here's the basics:
You need a server that is able to connect to the APNs whenever you have notifications for your app.
That server will then connect to the APNs using your Apple supplied SSL cert.
For each messages that you have to send:
a. Create a payload message that your app can do something with.
b. Include the deviceToken for the iPhone you want to send notifications to.
c. Write the raw data (see Apple's docs for specifics on the format) to the socket for each message.
Disconnect from the APNs.
What Apple means by "asynchronous", is that the APNs will not send a response to any of your data acknowledging it. So you need to make sure that whatever networking library you're using to connect can support raw data connections.
I don't think I have seen any published guidelines for minimum time between connections. I think Apple's note is more specifically directed to ensure that you're batching your messages and not flooding the APNs maliciously. I suspect that they'll contact you first if they feel you're overstepping the bounds.
Again, I would suggest a quick Google search on "iphone push notification tutorial" for specifics that can guide you further.
Hope this helps you on your way.