From: Jacques Garrigue <garrigue@math.nagoya-u.ac.jp>
To: n8gray@gmail.com
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Re: Select on channels (again)
Date: Tue, 22 Aug 2006 17:21:38 +0900 (JST) [thread overview]
Message-ID: <20060822.172138.82692882.garrigue@math.nagoya-u.ac.jp> (raw)
In-Reply-To: <aee06c9e0608212327y25e87a11wa52b40a1653a2d55@mail.gmail.com>
From: "Nathaniel Gray" <n8gray@gmail.com>
> On 8/21/06, Jonathan Roewen <jonathan.roewen@gmail.com> wrote:
> > Why can't you just use the unix file opening functions since you're
> > using unix select? And if you need the ocaml in/out channels, convert
> > the unix file descriptors to ocaml ones instead of the other way
> > around. Seems simple enough to me.
>
> It sounds simple but doesn't work. If select tells you a file
> descriptor doesn't have data waiting you can't be sure there isn't
> still data in the corresponding channel's buffer. See the thread that
> I referenced for a good discussion of why this is annoying. For one
> thing, it makes it impossible to use Marshal.from_channel without
> potentially blocking.
(I didn't follow the discussion, so I may misunderstand...)
The problem with Marshal.from_channel seems independent of channel
buffering. The point is that Marshal.from_channel cannot work in
non-blocking mode, as it doesn't know in advance how many bytes it
will need to obtain a well-formed value. The only way I see is to do
the buffering yourself, and extract the data using Marshal.from_string
and Marshal.total_size.
Jacques Garrigue
next prev parent reply other threads:[~2006-08-22 8:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-15 0:46 Nathaniel Gray
2006-08-21 22:47 ` Nathaniel Gray
2006-08-22 0:42 ` [Caml-list] " Jonathan Roewen
2006-08-22 6:27 ` Nathaniel Gray
2006-08-22 6:41 ` Jonathan Roewen
2006-08-22 8:15 ` skaller
2006-08-22 21:15 ` Mike Lin
2006-08-23 5:12 ` Nathaniel Gray
2006-08-22 8:10 ` Olivier Andrieu
2006-08-23 5:27 ` Nathaniel Gray
2006-08-22 8:21 ` Jacques Garrigue [this message]
2006-08-23 5:16 ` Nathaniel Gray
2006-08-23 6:35 ` skaller
2006-08-23 19:31 ` Nathaniel Gray
2006-08-24 5:37 ` skaller
2006-08-24 19:06 ` Nathaniel Gray
2006-08-25 1:55 ` skaller
2006-08-25 22:19 ` Nathaniel Gray
2006-08-23 8:29 Christoph Bauer
2006-08-23 17:35 ` Robert Roessler
2006-08-24 8:18 ` Robert Roessler
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=20060822.172138.82692882.garrigue@math.nagoya-u.ac.jp \
--to=garrigue@math.nagoya-u.ac.jp \
--cc=caml-list@yquem.inria.fr \
--cc=n8gray@gmail.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;
as well as URLs for NNTP newsgroup(s).