From: Gerd Stolpmann <info@gerd-stolpmann.de>
To: David Allsopp <dra-news@metastack.com>
Cc: OCaml List <caml-list@inria.fr>
Subject: Re: [Caml-list] Writing to a blocked socket
Date: Tue, 02 Aug 2011 21:16:01 +0200 [thread overview]
Message-ID: <1312312561.6236.307.camel@thinkpad> (raw)
In-Reply-To: <000101cc5135$e1f1ab90$a5d502b0$@metastack.com>
Am Dienstag, den 02.08.2011, 18:01 +0100 schrieb David Allsopp:
> 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?
Really? This does not make sense at all. It's quite normal that one
direction is blocked, and the other not. Are you sure about your
observation?
Gerd
>
>
> 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)]
>
>
--
------------------------------------------------------------
Gerd Stolpmann, Darmstadt, Germany gerd@gerd-stolpmann.de
Creator of GODI and camlcity.org.
Contact details: http://www.camlcity.org/contact.html
Company homepage: http://www.gerd-stolpmann.de
*** Searching for new projects! Need consulting for system
*** programming in Ocaml? Gerd Stolpmann can help you.
------------------------------------------------------------
next prev parent reply other threads:[~2011-08-02 19:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-02 17:01 David Allsopp
2011-08-02 19:16 ` Gerd Stolpmann [this message]
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=1312312561.6236.307.camel@thinkpad \
--to=info@gerd-stolpmann.de \
--cc=caml-list@inria.fr \
--cc=dra-news@metastack.com \
/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