From: Lyndon Nerenberg <lyndon@orthanc.ca>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] dns vs. textrr
Date: Thu, 19 Jan 2012 15:32:11 -0800 [thread overview]
Message-ID: <EB9FA4E6-D6CC-401D-90A2-852E26FBBAD0@orthanc.ca> (raw)
In-Reply-To: <1f84be967187ad0ab70e35a0fc1f7063@coraid.com>
On 2012-01-19, at 2:12 PM, erik quanstrom wrote:
> that seems a bit ... goofy. it would seem better for
> bio to do this internally? surely there isn't code that
> relies on this behavior?
Or maybe realloc() a larger buffer and try to carry on? There's no guarantee of buffer pointer consistency across B* calls, is there? Default to 8K (or whatever), and place an adjustable cap of, say, 128K, on the dynamic bsize.
Given some XML stanzas I've seen lately, elastic buffers have a lot of appeal ...
next prev parent reply other threads:[~2012-01-19 23:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-19 16:01 erik quanstrom
2012-01-19 17:00 ` Jeff Sickel
2012-01-19 17:17 ` erik quanstrom
2012-01-19 22:12 ` erik quanstrom
2012-01-19 23:32 ` Lyndon Nerenberg [this message]
2012-01-19 23:56 ` erik quanstrom
2012-01-20 0:11 ` Lyndon Nerenberg
2012-01-20 0:14 ` erik quanstrom
2012-01-20 0:39 ` Lyndon Nerenberg
2012-01-20 6:31 ` Jeff Sickel
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=EB9FA4E6-D6CC-401D-90A2-852E26FBBAD0@orthanc.ca \
--to=lyndon@orthanc.ca \
--cc=9fans@9fans.net \
/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).