There are lots of issues with implementing push technology, here are just a few:
You are looking at the application layer, you need to be concerned about the transport layer(s). How does your server know the address (IP or other) of the phone? It gets assigned by DHCP and whenever the connection is broken/dropped for any reason it can be given a different IP address by the telecommunications provider. If you are connecting from the phone to the server to when the phone's IP address changes you may as well keep the channel open and pull the data down. With a WiFi connection the phone is probably on the inside of a NAT router so again making an incoming connection to the phone is not going to work. So many problems, you are probably best just sending an SMS message containing a url to your web server and getting the end-user to click on it. -- RichardC On Oct 16, 3:43 pm, rubeN_vl <rvanluch...@hotmail.com> wrote: > Hi, > > What are the different ways to implement push technology into your > Android app? > The client Android app is supposed to receive content (XML Data) > pushed by the server. > I've looked around and found out it was possible to achieve it with > usage off the SOAP protocol. > But are there some better ways top implement push? > The main concern in this project is the phones battery life, all off > it has to happpen over WiFi, pushed content has to be viewable on the > device immediately. > > Thoughts and/or sample code is welcome! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
