Dear all,
we are using MonoTouch 3.0.3.4 and we have discovered a problem with the socket
class. Our application uses TCP sockets and we found out that occasionally upon
socket closure (after some data has been sent and received) the application
hangs in socket.Close() method. We do not use any linger interval, so there
should be absolutely no reason for the socket.Close method to wait for
anything. This happens with and also without calling Shutdown before Close.
From what we saw in the Assembly Browser, Close calls socket.Dispose which
calls some other methods like Linger etc. which might be the cause for the
Close call to block.
Is this a bug or is there a way / workaround to make an abortive socket close
without any waits?
Also, from what we have seen in the socket.Dispose method, the Close method
might end up with an exception, but AFAIK there is no exception documented for
the socket.Close method in .NET. This might be dangerous when you do not expect
any exception here.
Thanks for any suggestions.
Alex
_______________________________________________
MonoTouch mailing list
[email protected]
http://lists.ximian.com/mailman/listinfo/monotouch
