SocketIO for Mobile 

Co Travelling in a Small World

Author: Pronab Pal, Technical Architect, TCS

HTTP/SOAP

*Redundant Payload [xml and http headers etc-legacy]

*expensive[thread bound] network connect

* dedicated mobile resouce

for the time of transaction

*synchronous request 

response ties up resources  

Socket/JSON

* min management  payload

* duplex ,event driven connection

* cheap node.js connections

asynchronous i/o

* mobile resources free during transaction execution

* asynchronous call

Benefits

• In Apps Browser/WebView/Native allways in Sync
• Client profile specific intelligence
• Response faster
• json structure on mobile side
• better connection usage with GDS
• Cotravelling: imagine your favourite  magician,author,game player,chef interacting with you on device travelling on the same boat,plane,car etc.

But..do I need it ?

If I have enough resource ?

I am just waiting for new customers?

I have big power machines

Good Question:

Answer is in the attitude towards customers

Do you see the co-travelling experience of customers as a important piece in your business ?

Answer yes? then you need it.