caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Robert Roessler <roessler@rftp.com>
To: Caml-list <caml-list@inria.fr>
Subject: Re: AW: [Caml-list] Re: Select on channels (again)
Date: Wed, 23 Aug 2006 00:44:36 -0700	[thread overview]
Message-ID: <44EC0764.50306@rftp.com> (raw)
In-Reply-To: <26EB47FDD566A7469FC862DAF373792F018CF5D0@kaiserslautern1.lmsintl.com>

Christoph Bauer wrote:
> ...
> I did this, but on windows with two programs communicating over
> a pipe this isn't enough. select on windows and on a pipe doesn't
> work. Therefore I wrote a stub for PeekNamedPipe():

"Select on windows" certainly does work... and why not use a socket 
pair, just as one might on a *nix system?  That way, it will work on both.

And the fact that socketpair has been left out of the Windows version 
of the Unix module is not an impediment - it is easy to write a useful 
implementation in OCaml (I can supply one if needed).

Robert Roessler
roessler@rftp.com
http://www.rftp.com


      reply	other threads:[~2006-08-23  7:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-23  7:02 Christoph Bauer
2006-08-23  7:44 ` Robert Roessler [this message]

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=44EC0764.50306@rftp.com \
    --to=roessler@rftp.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).