deepstream.io client for Android

[deepstreamio]

deepstream.io client for Android

@yasserf Nice, thanks!!

[hopewise]

Can I use other WebSocket clients for android with deepstream ? like AndroidAsync ? https://github.com/koush/AndroidAsync

[yasserf]

The two transport methods currently supported are engine.io and TCP connections.

You could use the engine.io-client-java library to support the engine.io layer. The API should be consistent with the one we are currently using for the browser client. If using websockets directly you would have to add a thin compatability layer ontop to get it to work correctly.

The other alternative is to use the native Java TCP client. This means we could send more messages across with less overhead, a win specially for mobiles! Main benefit of this approach is that we could have a Java library which is wrapped for Android which is a double win.

I haven't done that in a while though so am curious to hear your thoughts!

[hopewise]

Thanks yasserf for valuable suggestions, I can't give an advice here, sense I am not an experienced java or android developer, never the less, I will be connecting the pieces to build a proof of concept for our project.

Native Java TCP client will be better for those real time educational apps, teacher will be drawing something and students watch the drawing, such scenario needs more messages for sure..

I think a message each 5 seconds is sufficient for my case, as we will be tracking car drivers via mobiles.

This is my humble thoughts, will it be a good choice for using engine.io-client-java for our case?
I will test will deepstream with engine.io-client-java as soon as I have the time.

[yasserf]

hey hopewise,

Proof of concepts are usually a great way to start, if you get blocked feel free to contact me on the slack channel or here. Haven't done Java in a while but it's that language you always run into at some point =P

Regarding the connection type:

Using the http/s protocol is required if in production your server/firewalls only has http/s ports available. That's mainly where engine.io is awesome, since it simulates what a bidirectional tcp connection would look like, except using long-polling or websockets depending on your network configuration / device support.

If you look at the connection class in the javascript client you'll notice it abstracts away the endpoint itself. If you could follow the same design concept it means we could easily switch between tcp and engine.io connections via application configuration and not be restricted to either.

[yasserf]

Update: We'll attempt to usine the java sdk (#66) as a base for the android client. If anyone is aware of any issues from using native java (1.7) code in an android app please let me know!

@yasserf could please update gradle for deepstream.io-client-java? because the latest code from last commit not there . Thanks.

[yasserf]

should be done, version 0.6!

@yasserf sorry that bothering you, but issue in v.0.6 still exist. Could you pls check again.

[yasserf]

hey! Very sorry about that :$, I think their was a commit mixup.

I don't have my dev env setup on this machine, but will do it first thing 2moro morning.

[yasserf]

@fair18 should be done now!

[yasserf]

Closing as issues can be raised against java repo