I developed a Blackberry Native application and now the client want notifications even when the device is turned-off. After a few searching, Blackberry Push Service seems the way to go, but i have some concerns:
Blackberry Push Service is a free or paid service?
What are the library requirements on the client side? Do I need additional libraries or it only work with Blackberry SDK?
How are the notifications sent? Do I need to build an additional application for that? The client has IIS servers, so I wanna know if it is possible to build such an application in .NET.
Have any one tried Urban Airship? Seems like a simpler way to accomplish the task.
RIM charges for Push services based on how much data you are pushing through their servers, and for delivery confirmation. If your customer base is small, and the push data requirements are modest they won't charge anything.
When you register to start a push service they will send you sample code but there are no additional library requirements.
Push notifications are XML documents that are POSTed to a RIM 'web' server. There are a number of services you must provide to the client for registration and push control. The standard way of doing this is again with a 'web' server that RIM and the client device communicate with. When you register RIM will send you a sample server module designed to run in Apache TomCat, but I (and others) have replicated the necessary capability on Linux, Apache, MySQL, and PHP servers (LAMPS). I don't see any reason you could not implement this on IIS but I have no experience with IIS. (I put 'web' in quotes because this server may, but does not have to, serve any web pages in the traditional sense. The push service uses HTTPS as the transport protocol.)
I don't even know what that is.
If your client is running a BES then they already have everything they need to push to the client and get delivery confirmation without any additional cost. JP Mens published a very good article on using the BES MDS server to push data to clients from a LAMPS machine.
Related
Is there any way to create your own google IOT device based on webhooks and POST-request? Without using firebase, IFTT, node.js
Samples that Google are very poor, they don`t show all steps of creating your own app, they just showing how to deploy "their sample"
I tried to make action with dialogflow & webhook, it was pretty simple. Just processed JSON in POST request to Azure function.
But when I try to create IOT device, its ask me for fulfilment url and it does not even tries to reach that address. I read about action.device.sync, action.device.execute, it just does not communicate with the specified address, giving simulator some voice command doesn`t affect at all. Are there any ways to create IOT device to work with POST-requests & web-hooks?
The answer is it depends.
There are many different ways to do server-device communication: web sockets, local servers, hub/local control, polling, MQTT, and likely many others. All of these solutions have trade-offs, and work in particular circumstances. Depending on exactly what IoT device you want to build, its requirements and technical specs, and what cloud providers you are using, you may identify what works best.
If you run the sample, you'll see it is sending JSON requests to a server and expect JSON responses back. This is must like Dialogflow & a webhook. In this case, the smart home platform communicates solely with the server.
Your server can then communicate with the device in any way that you want. I'm not too familiar with Azure offerings. It might have an MQTT service as well, or some other sort of push notification service you might be able to use.
If you're seeing simulator issues, you may need to make sure your authentication is set up correctly, and you'll need to first complete account linking on your phone before you can use the simulator.
Is it possible to use OneSignal to create a native PushNotification to an iOS device from an asp.Net server? What's the difference between OneSignal and PushSharp? Is the difference that I would have to setup OneSignal on my mobile app instead of just allowing the app to hit endpoints on my server to register/unregister for pushNotifications(Which I was planning to use PushSharp for)
The webapp is currently being hosted on Azure, so the notification hub is an option too. But would the communication hub make me be tied down to azure?(Say I wanted to host my webapp on a different service and maybe change the server code to node)
On mobileApp startup, I'd like to send a request to the server to register the device token. It'd be best if I didn't have to config the app.
edit: I also contacted OneSignal with questions, I'll report back with any findings.
I want to build a instant messaging application using Ruby on Rails but I'm confused about the implementation.
How is a IM application (like the one on Facebook) usually implemented? I think we can use a push server (server pushes to client) or polling (client asks the server), but is there any other ways? And what are the corresponding advantages of these two approaches? Which one is usually more efficient and less demanding?
Thanks in advance.
Polling: In case of Polling, browser makes the request to server at a regular interval to check for updates. It will increase your server load.
Server Sent Events: server sent events.
Server-Sent Events have been designed from the ground up to be efficient. When communicating using SSEs, a server can push data to your app whenever it wants, without the need to make an initial request.
WebSockets: WebSockets on the other hand, require full-duplex connections and new Web Socket servers to handle the protocol.
For IM best suited is websocket, as using websocket you can do bi-directional communication.
A similar example of IM using websocket is Applozic chat SDK. It Uses web sockets for Real Time Messaging.
I don't know specifically how Facebook implements their IM service, but most web-based IM clients use either a push server or a Jabber client. Jabber is good if you want the users to be able to communicate with the service through their own IM client, and not just through the web frontend; push is good if you're doing something interesting with the received messages on the server-side. Polling isn't used anywhere near as widely nowadays. It requires the same JavaScript support as server push, but is much more resource-intensive for your server.
For getting started with push, I would recommend looking into Faye or Juggernaut.
If you're interested in Jabber options, check out the JavaScript Jabber Client Library.
Amazon Web Services have an SDK for iOS which supports the Amazon Simple Notification Service (SNS).
Does this mean it would be possible to use SNS to send push notifications to a running iOS app? So for example you could make an real-time instant messaging app.
Is this right, or have I misunderstood what SNS does? It just seems to me that you would need to open a connection/socket in order to recieve push notifications from your server. How does the SDK actually work?
Update:
I've since asked this question on the AWS Mobile Development Forum: https://forums.aws.amazon.com/thread.jspa?threadID=81089&tstart=0
Apparently there is an article coming out (probably here: http://aws.amazon.com/articles/SDKs/iOS) shortly to explain everything.
Update 2
The article: http://aws.amazon.com/articles/9156883257507082
According to Apple documentation "Local notifications and push notifications are ways for an application that isn’t running in the foreground to let its users know it has information for them.".
So, technically speaking, any data, including notifications, received when the application is running in the foreground are not "Push Notifications" and can't be a reason for rejecting the application. They're simply data being consumed that way or the other by the application.
In this specific case you are not asking about Push Notifications per Apple's documentation, rather about a technology used to deliver data to the application when the application is running and user is interacting with it. It happens that the name Amazon SNS is similar to Push Notification.
In any case Apple wouldn't be able to see what is the technology behind delivering data to your application, whether it is Amazon SNS or anything else. All they can see is that the application may have some additional ports open when it's running, and that of course would be absolutely legal. In fact, many applications communicate with their back-end servers using sockets (not HTTP requests), and that is the same technology as used by Apple to deliver their Push Notifications.
According to the Amazon documentation, they in turn uses the APNS method and provide a much simpler frontend for Apple, Android and Kindle. A realtime instant messaging app could be considered as workable since by using the Amazon SNS platform, you could even consider the application to be available for all.
I mean by utilizing the Amazon SNS, the communication could be done between iOS and Android devices and to kindle also provided the applications are written accordingly. Though the Amazon documents do not provide a comprehensive example, there are bits and pieces. Also there is an upcoming event on the Aug 29 which could be seen from the Amazon SNS page.
I have registered with RIM for the push notification evaluation. But i cant find good sources for implementing push notifications. There are some samples in the sdk but i couldnt find out a way to implement them. So, i am looking for a good tutorial where i could find step by step implementation of push notification services...
RIM's samples for the server side involve setting up a web application container (e.g. Tomcat), setting up a backend database, and then building their Spring-based application. This sample web app handles things like device registration, content subscription, etc. and features a portal to manage everything.
The bare minimum that is required, though, is to send a WAP Push message which is just an HTTP POST to their Push Service servers. Here is a thread from the BlackBerry Support Forums that describes how to use their low-level PAP API to construct this message. Pay attention in particular to the messages by the user mdicesare.
There's also another SO question that has some tips.