Actually, I've been using BSD sockets since about 1992 with about 10 OSes :)
The bug I mentioned is not a 'timeout', it is for connection refused which (as you know) should return immediately (network permitting) with a 'connection refused' error. With Android the socket read is sitting there for minutes after receiving the connection refused packet from the server.This is when testing on a local server. There is another bug related to closing a socket: when you close a socket from another thread it should cause any threads blocking on the socket to immediately return with an IOException, but this is not happening. This second bug is more serious because there is no way to interrupt the blocking thread. It appears that it is a bug in both the phones and the emulator. Next time you accuse someone of not knowing what they are talking about, you might want to check your facts first :) On Jun 9, 5:29 am, Anton Persson <[email protected]> wrote: > OK, the only example you bring up about ANDROID itself is the > IOException-part... That is not even a _bug_, that is a usage error. Have > you ever used BSD sockets in most other OS:es? It's up to you to handle > connection timeouts. TCP/IP over the globe, and over slow/delayed networks > will sometime cause big delays, so you can't just abort within a > milli-second each time. > > The other stuff is about developer environment specific stuff, and of them > only one is a real bug.. (The crash of the layout editor, which I agree is > serious, but I never used it myself so I don't know if it affects many > people..) -- 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
