From mboxrd@z Thu Jan  1 00:00:00 1970
From: YAMANASHI Takeshi <uncover@beat.cc.titech.ac.jp>
To: 9fans@cse.psu.edu
Mime-Version: 1.0 (generated by tm-edit 7.106)
Content-Type: text/plain; charset=US-ASCII
Message-ID: <12636.1008651053@beat.cc.titech.ac.jp>
Subject: [9fans] lib9p
Date: Tue, 18 Dec 2001 13:50:53 +0900
Topicbox-Message-UUID: 38c84974-eaca-11e9-9e20-41e7f4b1d025

I'm building a file server program on lib9p.

On providing the client read function, is it OK that the parent
process forks off a child and returns imediately, while the
child calls the respond() funtion after having done blocking
read() or something?  I'm concerning about the variable
'long *count' passed to srv->read() function for the sake of
returning the count of bytes.

I found srv() is calling the client read function as
	srv->read(r, r->fid, r->rbuf, &r->fcall.count, r->fcall.offset);
in /sys/src/lib9p/srv.c and doesn't care '*count' at all
after that.

So I think it's OK for the present.  But can I rely on it?
--
Sincerely,
YAMANASHI Takeshi