From: YAMANASHI Takeshi <uncover@beat.cc.titech.ac.jp>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] lib9p
Date: Wed, 19 Dec 2001 13:46:32 +0900 [thread overview]
Message-ID: <14331.1008737192@beat.cc.titech.ac.jp> (raw)
In-Reply-To: Your message of "Tue, 18 Dec 2001 11:31:13 EST." <20011218163114.C92FC199B5@mail.cse.psu.edu>
Hi.
> After you
> respond to a flush request you have to make sure that
> r->oldreq will never get responded to.
I agree. I'm pondering whether to make the parent to
kill the appropriate child in srv->flush(), or to make
the child to check validity of a Req *req before
calling respond(). Hmmm.
--
YAMANASHI Takeshi
next prev parent reply other threads:[~2001-12-19 4:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-18 16:31 Russ Cox
2001-12-19 4:46 ` YAMANASHI Takeshi [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-12-20 2:31 okamoto
2001-12-21 9:58 ` David Rubin
2001-12-20 1:59 okamoto
2001-12-20 2:25 ` YAMANASHI Takeshi
2001-12-18 5:00 Russ Cox
2001-12-18 8:17 ` YAMANASHI Takeshi
2001-12-19 14:04 ` David Rubin
2001-12-20 0:22 ` YAMANASHI Takeshi
2001-12-18 4:50 YAMANASHI Takeshi
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=14331.1008737192@beat.cc.titech.ac.jp \
--to=uncover@beat.cc.titech.ac.jp \
--cc=9fans@cse.psu.edu \
/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).