--On 16 September 2011 10:34:46 +0200 Wouter Verhelst <[email protected]> wrote:
> Of course, relying on TCP to do this does make it possible that both > the client and the server are writing to the socket at the same time > when one of them needs to do a read first before things can go on, > thereby deadlocking the connection. This is what happens with the > integrityhuge test on some platforms, which is why I've disabled it for > now Mmm.... if a server can't cope with client and server both writing to the socket at the same time, doesn't that illustrate a bug on the server? IE isn't the correct thing to do to fix the bug, not disable the test? Is this some form of deadlock you are talking about? -- Alex Bligh ------------------------------------------------------------------------------ BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA http://p.sf.net/sfu/rim-devcon-copy2 _______________________________________________ Nbd-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nbd-general
