Date: Sun, 4 Jan 2015 21:07:04 -0500 From: Phil Shafer <phil@juniper.net> To: Alfred Perlstein <bright@mu.org> Cc: Marcel Moolenaar <marcel@freebsd.org>, John-Mark Gurney <jmg@funkthat.com>, Alfred Perlstein <alfred@freebsd.org>, "Simon J. Gerraty" <sjg@juniper.net>, "arch@freebsd.org" <arch@freebsd.org>, Poul-Henning Kamp <phk@phk.freebsd.dk>, freebsd-arch <freebsd-arch@freebsd.org>, Konstantin Belousov <kostikbel@gmail.com> Subject: Re: Libxo bugs and fixes. Message-ID: <201501050207.t05274U2086589@idle.juniper.net> In-Reply-To: <B2197911-9DA2-420B-AB17-0DCF09D35799@mu.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Alfred Perlstein writes: >In the case of xo_flush_h() how does a subroutine know how to flush the backing object o >f the handle? Okay, I buy the argument that calling xo_flush should trigger a flush all the way down the stack. The app should be able to call xo_flush when it matters to the app, and the result should be a complete flush of output. Will get it working. Thanks, Phil
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201501050207.t05274U2086589>