Asynctask Better Communication Protocol
Solution 1:
AsyncTask is not obsolete (nor is it deprecated), but it's probably not a good choice for persistent socket communication. AsyncTask is better suited to relatively short-lived operations, including ones that make UI modifications to show progress or upon completion since the threading is handled for you. Because you can use AsyncTask to modify the UI, most people associate the AsyncTask with their Activity or some of its Views, which can be a problem since any configuration change may cause the Activity to be destroyed and recreated, but you will still have an AsyncTask living in memory holding on to the entire Activity context.
For something like a persistent socket, you are better off using a Service, which is a separate application component that won't go through configuration changes like Activitys do. You can also manage its lifecycle differently, whereas the Activity lifecycle is dictated primarily by user interaction. 
Solution 2:
You can use some http request library like "Volley" or "OkHttp" (my favorite)
Create your own server API to communicate like this:
- Phone send http request to an web API -> Web API receive the request, process and call Database 
- Database responses and send the data to the Web API -> Web API get the database response and send to your Phone -> Your phone receive the data 
You can use Json or XML for the data transfer (Prefer Json for the simplicity)
According to the android wiki, "AsyncTask" is not deprecated !
Solution 3:
You need to create state full connection using TCP / UDP protocol, both implement scoket programming then you will be able to pass data to android client. other work around is to use Google messaging (GCM) through GCM you can send data to your android application. OR you can use Open fire for socket programming.
Post a Comment for "Asynctask Better Communication Protocol"