What is disturbing is that event if you try to send data on a socket that is not actually connected (according to the situation I outlined initially) the socket does not throw an IOException. It simply thinks it is still connected.
On Feb 17, 7:21 am, Guillaume Perrot <guillaume.p...@gmail.com> wrote: > I had the same problem too. > Plus when I loose connectivity, it's nearly impossible not to block on > socket.close(); > It takes forever in that case. > I tried both plain and ssl sockets, same behavior in RC33. > > On Feb 17, 1:23 am, Marc <gram...@gmail.com> wrote: > > > I've seen inconsistent behavior from RC30 on in this regard. The > > IOException happens anywhere from instantly to five minutes later. It > > seems like a bug to me. > > > Marc > > > On Feb 16, 2:29 pm, Gil <virgildobjans...@gmail.com> wrote: > > > > I finally got to test some code on the RC33 release and I uncovered a > > > difference in the network code compared to earlier versions and the > > > emulator. I'm using a persistent TLS connection to a server and a > > > BufferedInputStream to read from the socket. The problem is that the > > > read method throws an IOException only 5 minutes after the Wi-Fi > > > connection looses connectivity (I unplug the Internet connection from > > > the router to simulate a connection problem). In RC30 and earlier > > > version as well as the latest emulator version (SDK 1.1) read throws > > > an exception after approximately 30 seconds after the connectivity is > > > lost. My code uses an infinite timeout for read (setSoTimeout(0)). --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
