That's quite interesting thanks TreKing. That is one approach but dont think it will work for me.
On scenario is if 200 phones connect to my server wanting to send one jpg to another phone. 200 messages would go out trough google notifying all phones there is jpg package for them. Google has Limitations in that C2DM about "Google limits the number of messages a sender sends in aggregate". Also possible lagging. My initial naive thought was that all those 200 phones could have an app installed that make a connection to me PC server and keep that connection alive. I'm searching for a best way to do do this. What would you do? - Services are bad design and a user might think his battery get drained - Activity with AsyncTask is beautiful if android not killing the app Hmmm (not sure there). One AsyncTask constantely listening for incoming and another AsyncTask gets created when user send jpg. Can an AsyncTask live that long, Is it possible to protect the AsyncTask from onCreate updates, orientationchanges? -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
