comp.lang.ada
 help / color / mirror / Atom feed
From: tmoran@acm.org
Subject: Re: API design problem - buffer scatter I/O
Date: Mon, 24 Nov 2008 18:16:26 +0100 (CET)
Date: 2008-11-24T18:16:26+01:00	[thread overview]
Message-ID: <ggenha$ute$1@aioe.org> (raw)
In-Reply-To: f980d11e-4113-41a8-9c24-bf2df53e18f8@a12g2000yqm.googlegroups.com

> The problem is that this is a single, continuous array.
> How would you approach the design of API for multi-buffer I/O? Multi-
> buffer means that the user can provide many arrays, probably of
> different sizes, and the library will fill them from first to last.
  Is this an actual problem?  In most systems copying the bytes from
an IO buffer into different places will be a small percentage of the
time taken by the actual IO, so the simplicity of a single IO buffer
is worth the modest cost.



  parent reply	other threads:[~2008-11-24 17:16 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-22 16:05 API design problem - buffer scatter I/O Maciej Sobczak
2008-11-22 16:54 ` sjw
2008-11-22 19:43 ` george.priv
2008-11-22 22:16 ` Robert A Duff
2008-11-22 23:34   ` Maciej Sobczak
2008-11-23  0:01     ` Robert A Duff
2008-11-24  8:10       ` Brad Moore
2008-11-24  7:55   ` christoph.grein
2008-11-24 20:03     ` Robert A Duff
2008-11-25  5:59       ` christoph.grein
2008-11-25  8:34         ` Dmitry A. Kazakov
2008-11-25 14:25         ` Robert A Duff
2008-11-25 22:20       ` Randy Brukardt
2008-11-24 21:23     ` Robert A Duff
2008-11-22 23:01 ` Georg Bauhaus
2008-11-23  5:57 ` anon
2008-11-24 17:16 ` tmoran [this message]
2008-11-26  8:34   ` Maciej Sobczak
2008-11-26 20:39     ` sjw
replies disabled

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox