Re: [9fans] 9p and how can I know when a write is finished

["Gabriel Diaz" <gabidiaz@gmail.com>]

Hello

Using "normal" files is quite easy to do like ramfs does,
but if you write commands to a file that should be parsed,
you should choose when will your parser run, just
in the fswrite call? if you receive multiple writes, may be
you end with a split command and your parser returning error.

The options people are saying are: wait for Tclunk or do special
write request like wikifs, or have a buffer that is managed with that
ctl.

and what i ask about is how the people handle this :)

Reading the responses i think i will try first buffering and parsing
when Tclunk.

gabi


On 3/1/06, Ronald G Minnich <rminnich@lanl.gov> wrote:
> uriel@cat-v.org wrote:
> >>On Wed, Mar 01, 2006 at 03:29:58PM +0100, Gabriel Diaz wrote:
>
> >>As far as I understood, you wait until Tclunk.
> >
> > Wrong, the Tclunk is not warranteed to arrive any time soon.
> >
> > Tclunk != close()
>
>
> you guys are all confusing me. AFAIK, if you have written a plan 9
> server, you have the standard Ye Olde Server Dispatche Functionne.
>
> Said function, when it gets a Req with an op type of Twrite, calls the
> appropriate server function, and replies.
>
> I just finished writing another one of these (A GPS server ... fun!) and
> it all Just Works.
>
> So, I don't see the problem. Plan 9 packet sizes can be pretty big ---
> much much bigger then the MTU on a network -- so the 9p server code
> deals with it. When your Twrite gets called, it has the data.
>
> ron
>