From: "David Allsopp" <dra-news@metastack.com>
To: "OCaml List" <caml-list@inria.fr>
Subject: [Caml-list] Writing to a blocked socket
Date: Tue, 2 Aug 2011 18:01:54 +0100 [thread overview]
Message-ID: <000101cc5135$e1f1ab90$a5d502b0$@metastack.com> (raw)
I don't seem to be able to ask Google this in a way which will give me a
reasonable answer!
In the same process, if you have one thread blocked on a [recv] operation on
a socket, under Unix another thread can still write to the socket. Under
Windows, however, the call to [send] blocks because there's another thread
blocked on a [recv] to the same socket. Are there any options that can be
set to change that behaviour or is that just "the way it is" and the
application has to be coded using [select] instead?
David
[the astute Mr Holmes may have spotted that having got ocaml-ssl built, I
then couldn't get its stelnet example to work ;o)]
next reply other threads:[~2011-08-02 17:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-02 17:01 David Allsopp [this message]
2011-08-02 19:16 ` Gerd Stolpmann
2011-08-02 20:17 ` David Allsopp
2011-08-02 20:41 ` David Allsopp
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='000101cc5135$e1f1ab90$a5d502b0$@metastack.com' \
--to=dra-news@metastack.com \
--cc=caml-list@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).