From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] fs error msg: didn't like (1460 274) byte message
Date: Wed, 25 Sep 2002 17:21:36 -0400 [thread overview]
Message-ID: <bd21b63040f25d3cb95a1874fd14e3e8@plan9.bell-labs.com> (raw)
> I tried something like that, and what I tried did not work, but my failure
> might differ from your xfer9p (have thrown it away, cannot compare).
> Still I'm wondering, why use own code instead of simply using read9pmsg?
The reason not to use read9pmsg is that I don't want to
get caught with a buffer that's not big enough, so I realloc
it (when necessary) after reading the header length.
You can't use read9pmsg to do that unless you know
basically everything about what read9pmsg is doing, at
which point it's easier not to use it.
Or rather, it would be easier, if I could manage to write
the correct five lines.
Russ
next reply other threads:[~2002-09-25 21:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-25 21:21 Russ Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-09-25 21:30 Russ Cox
2002-09-26 8:49 ` Axel Belinfante
2002-09-25 18:24 Russ Cox
2002-09-25 18:44 ` Axel Belinfante
2002-09-25 21:12 ` Axel Belinfante
2002-09-24 23:42 Russ Cox
2002-09-25 11:45 ` Axel Belinfante
2002-09-25 18:19 ` Axel Belinfante
2002-09-24 23:25 Axel Belinfante
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=bd21b63040f25d3cb95a1874fd14e3e8@plan9.bell-labs.com \
--to=rsc@plan9.bell-labs.com \
--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).