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?
If SockJS is not a good option for me, then would it be better than to build my messaging app with Socket.io + Node.js (using JavaScript). Socket.io seems to me have all needed client libraries for iOS (official library by Socket.IO guys) and Android (official library by Socket.IO guys).
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.
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
http://www.elabs.se/blog/66-using-websockets-in-native-ios-and-android-apps
https://www.cometchat.com/blog/ios-android-chat-mobile-sdk/
https://github.com/elabs/mobile-websocket-example
We have tested them, both Android-client (link) was given by #Amr K. Ismail and
this iOS-client (link) are suitable with Spring-SockJS-Server which has STOMP.
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:
https://github.com/jeremyfa/openfl-sockjs
Not tested how well it works, but at least for Android it's using JavaScript from inside WebView, so should be no different than JavaScript one. Again, it is not clear how tightly it is coupled with OpenFL, but the approach of using WebView and stock SockJS client could probably be re-used.
How to Write a Java based Spring Web Socket (STOMP) Client. As in Spring we have only javascript based client is provided using stompJS but if we need a java client how should we need to achive it?
Spring 4.1 introduces a SockJs Java Client which is quite useful for server to server communication and performance testing. It doesn't come with a Stomp client (this is certainly in the roadmap) but you can check out the tests in the sample app which has already an implementation. Seems this is what you are looking for.
Update 8 Sep 2015:
Spring 4.2 has a STOMP Java client which can be used along with the SockJS Java client. More: https://docs.spring.io/spring/docs/4.2.x/spring-framework-reference/htmlsingle/#websocket-stomp-client
I would look for websocket clients in Java and build off of those. It seems that Jetty has a websocket client api as does too tall nate.
Currently, i'm working on android project. I have to join a jms server based on openJMS.
i've not found any library, anyone know how to implement JMS client on Android ?
thx.
Use the Kaazing WebSocket Gateway Android JMS Client API
you can visit Kaazing official website for that.
Thanks!
We have also faced same scenario.
You can use the Kaazing WebSocket Gateway to connect Android (and other) clients to JMS over WebSocket
Checklist: Build Android JMS Clients.
Channel API it is feature of GAE or feature of GWT? Can I use Channel API with simple GWT RemoteServiceServlet? (my app dont use GAE)
Channel API is a GAE API, so yes you can use it only within the GAE environment. If you are planing to deploy your servlets in GAE, you can still use channel API.
If you are not planning to use GAE as your server, and only use GWT on client/UI side, then you can use other options like Comet (Check link at http://caucho.com/resin-3.1/examples/servlet-comet/ for an example). I am not much aware of other "push" APIs, but some search would give you answers.
Also check http://tomcat.apache.org/tomcat-6.0-doc/aio.html
I'm creating a web app that runs on Google App Engine. I'm also developing a desktop client that needs to access/update data on the webapp.
I would like to create a web sevice api between the server and the client. What would be my best options?
According to GAE the do not support RMI og JAX out of the box.
I hate to answer my own question but Restlet is working on a GAE version. The current development version seems to work well.
http://wiki.restlet.org/docs_1.2/13-restlet/252-restlet.html