--nextPart1422456.JUAdqAIpzI
Content-Type: multipart/alternative;
boundary="Boundary-01=_MGJjJvCHGbcLoy5"
Content-Transfer-Encoding: 7bit
--Boundary-01=_MGJjJvCHGbcLoy5
Content-Type: text/plain;
charset="iso-8859-15"
Content-Transfer-Encoding: quoted-printable
On Friday 06 February 2009, David Faure wrote:
> On Tuesday 20 January 2009, Thiago Macieira wrote:
> > The problem with buffered mode is that write() will report that it wrote
> > all bytes, but the saving of them to disk might fail. In that case, the
> > write happens inside flush()
>
> So a solution is to test the return value of flush(), right? That's
> actually easier than checking each and every write() call... (and much mo=
re
> performant than using Unbuffered).
>
> When does flush happen if not called explicitely? In close? So we should =
do
> this?
There's no guarantee that in buffered mode write() won't actually have to=20
write to disk though, is there? We know that pending changes will have bee=
n=20
written out by flush() but there's no reason that write() won't actually wr=
ite=20
if its own internal buffers fill up.
Regards,
- Michael Pyne
--Boundary-01=_MGJjJvCHGbcLoy5
Content-Type: text/html;
charset="iso-8859-15"
Content-Transfer-Encoding: 7bit
On Friday 06 February 2009, David Faure wrote:
> On Tuesday 20 January 2009, Thiago Macieira wrote:
> > The problem with buffered mode is that write() will report that it wrote
> > all bytes, but the saving of them to disk might fail. In that case, the
> > write happens inside flush()
>
> So a solution is to test the return value of flush(), right? That's
> actually easier than checking each and every write() call... (and much more
> performant than using Unbuffered).
>
> When does flush happen if not called explicitely? In close? So we should do
> this?
There's no guarantee that in buffered mode write() won't actually have to write to disk though, is there? We know that pending changes will have been written out by flush() but there's no reason that write() won't actually write if its own internal buffers fill up.
Regards,
- Michael Pyne
--Boundary-01=_MGJjJvCHGbcLoy5--
--nextPart1422456.JUAdqAIpzI
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
iEYEABECAAYFAkmMkYwACgkQqjQYp5Omm0qvdgCguI8SEli0j0+JtprG462emS89
eA4An1yf1ZP2vJ2Rdjt8TSdu14wpHJW1
=H44Q
-----END PGP SIGNATURE-----
--nextPart1422456.JUAdqAIpzI--