I want to know if gcm(Google Cloud Message) has broadcast api in server now. I want to push notification without register_ids.I am not sure there is a broadcast api in server. Does someone know?
GCM 3 supports topic messaging: https://developers.google.com/cloud-messaging/topic-messaging
Related
Is it possible to configure Firebase app server to receive notification when there are messages exchanged between two other devices over Firebase Cloud Messaging?
So for instance I want to save these messages via my app server to the database. Currently I do it with additional REST request when I receive message on target phone.
However I want to avoid two jobs on target devices(listening/receiving the message and sending a request to save it) I'm thinking there must be an option where User sends a message from their phone and it not only arrives at target device but also notifies server?
There is no way to register your own observer that hooks in to Firebase Cloud Messaging's message sending mechanism.
There is also no capability to send messages directly from one device to another. There is always a piece of code that you deploy to a trusted environment (e.g. an app server of Cloud Functions) involved in sending so-called downstream messages to devices.
Two approaches that may accomplish the same need are:
Implement an XMPP server that sits between the devices sending messages and the FCM server that delivers messages to devices
Implement an intermediate service where the devices send the message, which then in turn calls FCM. This is a more generic approach of the previous one and is described in this blog post and in this use-case in the Cloud Functions for Firebase documentation.
Hi I am developing a chat application using XMPP. Consider the situation in the chat application, When User A send messages to User B and if the User B is offline at that time XMPP will store the sms as offline message and it will send that messages to User B when it comes online. This is working here. But I want to send this offline messages from XMPP as push to User B. I have done lots of searching and I came in a conclusion that we need to send the offline messages from XMPP server to our backend server and from there we need to send that message as push. But how to do this, please help me
It is possible to write a custom module to do that with ejabberd API.
What you need is to use mod_offline_hook (see ejabberd Events and Hooks) to be called when the server wants to store a message in offline store.
You can read mod_offline module for inspiration.
I am trying to figure out, once we send an email to X number of recipients through Amazon SES, how are we supposed to receive a bounce message (through Amazon SNS or any other tool) if we do not want them to be emailed to another account?
Using the nested labyrinth of Amazon's documentation, I found out one can have your bounces emailed to a specific account. But let us not take that path! The alternative is Configuring Amazon SNS Notifications for Amazon SES.
Here, Amazon offers two options:
Configuring Notifications Using the Amazon SES Console
Configuring Notifications Using the Amazon SES API
In the latter approach, Amazon introduces three API methods to deal with and writes
You can use these API actions to write a customized front-end
application for notifications.
Does "a customized front-end application for notifications" means setting up a Web server to listen for Bounce and Complaint JSON messages from Amazon?
No, you don't need a webserver to process the bounces, but you do need something to process them.
You tell SES which SNS topic to send the bounces too, and then you can subscribe to that SNS topic with a variety of endpoints of your choosing, getting an email is just one of them.
I find it best to let SES Notify SNS, and then have SNS deliver that message to an SQS queue, and I have a services that polls that queue and processes the bounces against my database.
AWS gives you the tools to be notified about bounces, but you still need to do the work of processing the bounce notifications.
The documentation is fairly clear. SES bounce notifications go to an SNS topic. Once you understand that you just need to look at the SNS documentation to see what methods are available to subscribe to an SNS topic. Currently the following methods of receiving SNS messages are available
Lambda
SQS
HTTP/S
Email
SMS
So you can have a Lambda function that gets called once for every bounce message. You can have bounce messages added to an SQS queue. You can have an HTTP/S endpoint in your application that bounce messages will get posted to. You can have bounce messages emailed to you. You can have bounce messages sent to your phone as SMS messages.
We are developing an app with a chat feature. We have an ejabberd (15.02) configured to use mod_offline_post to use the offline message hook and forward all messages for offline clients to an url of our own which then forwards to the GCM.
However as we are developing an app, we also need XEP-198 (stream management) enabled to handle connection loss. This is working fine in itself. Streams are created and resumed, messages are acknowledged.
The problem is, that the jabber is waiting for a stream to resume and is not forwarding any offline messages to the offline message hook and thus to our mod and post url. It is storing them in its offline storage of course and they get delivered when the recipient resumes its stream.
Is there any way to configure the jabber to call the offline message hook while ejabberd_c2s:fsm_next_state:2517 Waiting for resumption of stream for... ?
PS: We use smack on the client side to provide stream management
In my understanding the behaviour of ejabberd is correct from the XMPP specification point of view. It is doing the right thing and should not in that case forward message to the offline store, because you are not offline technically.
It is just not the right place to place your push processing.
I'm kind of starting programmer and on Objective-C. So I want to make an app for iOS that receives messages from a server. These messages are inputed manually, and send to all iOS connected to the server. People connected will receive a Push Notification, if they aren't connected to internet they will receive when they do and run the app.
So my question is: do I need to use a server to do this (sending messages for multiple iPhones)? In case of yes, with is the best server? TCP/socket?
If your only purpose behind using is to send push notifictaion message, then you dont need to spend on that. There are some service providers available which allow you to send notification from there website. for ex: you can use urbanairship. You need to register device token from your Xcode project using their SDK, and then you can send notification from their website.
Thanks!