Connect with iOS and Android clients to SockJS Backend
I’m developing WebSocket messaging backend using Spring WebSockets, which uses SockJS + STOMP protocol. The reason why not to use plain WebSockets is because I will need to leverage security integration that SockJS provides in Spring WebSockets and also other neat features from SockJS, such as rooms, subscriptions, etc. I was wondering if this is a good option to use so that mobile (iOS and Android) and Web client apps can easily connect to the backend server and perform messaging. If yes, then what libraries I can use for iOS and Android.
On SockJS GitHub page they are also listing available client libraries, but no iOS nor Android. So, I’m wondering if SockJS is even worth to use just because of that.
I found that for iOS client Primus-Objc (GitHub page) library claiming that they can connect to
native WebSockets, Socket.IO, SockJS or perhaps engine.io. is that a true statement? And event if that’s true, what about the quality of that library?
And event if it is ok to use SockJS on the back, then would it be also possible to show an example code for iOS and Android so that I can perform a proof of concept on mobile devices?
Another option can be to use Netty-Socket.io library and build each endpoint manually without any help from Spring Framework (which I’m considering to use) but there is small challenge that I’ll have to tackle, that is security. Somebody actually already tried to do it (the same author asking question on the official Netty-Socket.IO Github page) but looks like he didn’t have a luck in solving it yet.
3 Solutions Collect From Internet About “Connect with iOS and Android clients to SockJS Backend”
Maybe it’s more than a year since the question was asked. But, because it’s getting in the first results when Googling for SockJS+Android. So, I am posting my answer.
From my experience with a recent project I worked on, we were able to use a STOMP client – like the one here- to connect to Spring Websocket backend from native Android app.
And from the browser, you can still use SockJS client to gain across browsers compatibility to websockets with fallback.
A note to mention that when using only STOMP client to connect to native websocket the URL will be something like ws://mydomain/SockJSEndpoint/websocket,
and when using SockJS client from the browser the URL will be like http://mydomain/SockJSEndpoint.
Please find below useful references related to your requirement for both iOS and Android
SockJS may be interesting because it provides non-ws transports. Just using WebSockets may not be possible in all situations.
There is one cross-platform SockJs client of the OpenFL project:
- UIWebView doesn't seem to be loading the page
- draw embossed arc using core graphics
- Can't launch QtCreator debugger since XCode update to version 6
- How to create IPA in Xcode 6?
- Reduce the Xcode Simulator (Retina 4 inch)
- Why PFRelation does not support fromLocalDataStore queries?
- Iphone app archive – No such file or directory
- Screen tearing and camera capture with Metal
- AVSpeechSynthesizer error AudioSession
- How to get today's date in the Gregorian format when phone calendar is non-Gregorian?
- User made from Realm object has same Primary Key Realm
- Swift 3 UIView animation
- fake va_list in ARC
- Using a custom image for a UITableViewCell's accessoryView and having it respond to UITableViewDelegate
- Bluetooth Example Code for Cocoa (Objective-C)