Switching Towers does not drop the connection. What will drop is changing phone's IP or handoff...
regards 2008/10/8 Josh Roesslein <[EMAIL PROTECTED]> > I think you should be fine with a persistent connection. It might affect > the battery life a bit, but if you need live data then its really your only > option. > Only issue you might have is the connection getting dropped due to signal > lose or maybe when the phone switches cells (not sure if the network > preserves the connections between towers). > But you can always reconnect when this happens. > > > On Wed, Oct 8, 2008 at 2:36 PM, jay <[EMAIL PROTECTED]> wrote: > >> >> You could try running a server socket on the phone. The server would >> connect to the phone's port when it has something to send down and >> then tear it down. If TCP is too heavy handed for this, you could try >> using UDP (DatagramSocket) >> >> If T-Mobile has a NAT like router/firewall between the phone and the >> server, the server will not be able to reach the phone directly. Any >> body know if this is the case with T-Mobile? >> >> On Oct 8, 2:04 pm, j <[EMAIL PROTECTED]> wrote: >> > I would like to maintain a persistent socket connection to a server >> > via my background Service. The reason is I want to be able to push >> > notification data to client with minimal delay. Is there any problem >> > with this approach besides negative effects on the battery? >> >> > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
