TangORB for Android - TANGO Controls

# 9 years ago
kpitolin	Hi, I wanted to know if anyone had tried to use the TangORB for Android. If so : - is it possible to develop with it a standalone android client that can access device servers data and commands (of other equipments available on the bus)? - what would be the performances like compared to a REST architecture with a web server like this one : https://bitbucket.org/hzgwpn/mtango/wiki/mTango%20REST%20API doing the interface between the device servers and the android client? I thank you in advance for sharing your thoughts, Pitolin K.

# 9 years ago

Hi,
I wanted to know if anyone had tried to use the TangORB for Android.
If so :
- is it possible to develop with it a standalone android client that can access device servers data and commands (of other equipments available on the bus)?
- what would be the performances like compared to a REST architecture with a web server like this one : https://bitbucket.org/hzgwpn/mtango/wiki/mTango%20REST%20API doing the interface between the device servers and the android client?

I thank you in advance for sharing your thoughts,
Pitolin K.

# 9 years ago
Andy	Hi, the Android port of TangORB is being used by the Solaris synchrotron. They presented their project at the TANGO meeting last week. They added an extra layer for security using SSL. You should contact them to find out more about this. The device access is direct just like from a Java client so it should be faster than the REST interface. Kind regards Andy

# 9 years ago
kpitolin	Thank you very much Andy. I didn't even have to wait : you responded almost instantly ! I will contact them. Best regards, Pitolin K.

# 9 years ago
Ingvord	Yes, Andy is totally right. I have made a simple comparison: - read sys/tg_test/1/double_scalar for 10K times; - measure total time. TangORB approach gives 8,5 ms for a request in average while http – 35 ms. Serving http in this case consumes ~30 ms and it is normally a bad practice to use it for such small requests. On the other hand one can use builtin in Android http classes, i.e. no 3rd party libraries are required at all including TangORB.

# 9 years ago

Ingvord

Yes, Andy is totally right.

I have made a simple comparison:
- read sys/tg_test/1/double_scalar for 10K times;
- measure total time.
TangORB approach gives 8,5 ms for a request in average while http – 35 ms. Serving http in this case consumes ~30 ms and it is normally a bad practice to use it for such small requests. On the other hand one can use builtin in Android http classes, i.e. no 3rd party libraries are required at all including TangORB.

# 9 years ago
kpitolin	Thanks for your figures Ingvord. Are they any limitations with the TANGORB approach ? Is there something you can do with the REST approach that's impossible to do (for now) with TANGORB ?

# 9 years ago
Ingvord	I have no large experience with TangORB actually. As it is only for android and my main target is web I got no chance to use it.

# 8 years ago
giacomos	Hello Andy, hello everybody. Can you please point out where I can find this TangoORB for android? I thought the only android interface was this one: https://bitbucket.org/hzgwpn/mtango/wiki/mTango%20REST%20API Thanks in advance Giacomo.