From: Randi Botse <nightdecoder@gmail.com>
To: Sam Liao <phyomh@gmail.com>, linux-c-programming@vger.kernel.org
Subject: Re: select() timeout question
Date: Wed, 25 Nov 2009 03:58:26 -0500 [thread overview]
Message-ID: <34e1241d0911250058j47bb2bebo8a8763b4188b8541@mail.gmail.com> (raw)
In-Reply-To: <da5b0fda0911250038k4f6b87e7o3fd39e4c2db5ce86@mail.gmail.com>
Hi Sam,
That's means the data is buffered right?, is it guaranteed?
- Randi
On Wed, Nov 25, 2009 at 3:38 AM, Sam Liao <phyomh@gmail.com> wrote:
> You will get the data for next select call.
>
> -Sam
next prev parent reply other threads:[~2009-11-25 8:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-25 8:29 select() timeout question Randi Botse
[not found] ` <da5b0fda0911250038k4f6b87e7o3fd39e4c2db5ce86@mail.gmail.com>
2009-11-25 8:58 ` Randi Botse [this message]
2009-11-25 9:43 ` Michał Nazarewicz
2009-11-25 11:52 ` Randi Botse
2009-11-26 0:57 ` Helight.Xu
-- strict thread matches above, loose matches on Subject: below --
2009-11-28 5:43 Ardhan Madras
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=34e1241d0911250058j47bb2bebo8a8763b4188b8541@mail.gmail.com \
--to=nightdecoder@gmail.com \
--cc=linux-c-programming@vger.kernel.org \
--cc=phyomh@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).