/************************************************************************* * * DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER. * * Copyright 2000, 2010 Oracle and/or its affiliates. * * OpenOffice.org - a multi-platform office productivity suite * * This file is part of OpenOffice.org. * * OpenOffice.org is free software: you can redistribute it and/or modify * it under the terms of the GNU Lesser General Public License version 3 * only, as published by the Free Software Foundation. * * OpenOffice.org is distributed in the hope that it will be useful, * but WITHOUT ANY WARRANTY; without even the implied warranty of * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the * GNU Lesser General Public License version 3 for more details * (a copy is included in the LICENSE file that accompanied this code). * * You should have received a copy of the GNU Lesser General Public License * version 3 along with OpenOffice.org. If not, see * * for a copy of the LGPLv3 License. * ************************************************************************/ #ifndef __com_sun_star_io_XAsyncOutputMonitor_idl__ #define __com_sun_star_io_XAsyncOutputMonitor_idl__ #ifndef __com_sun_star_io_IOException_idl__ #include "com/sun/star/io/IOException.idl" #endif #ifndef __com_sun_star_uno_XInterface_idl__ #include "com/sun/star/uno/XInterface.idl" #endif module com { module sun { module star { module io { /** An optional companion interface to XOutputStream that supports scenarios where XOutputStream::writeBytes operates asynchronously and does not necessarily report any errors.

A typical scenario where this interface is useful is when an XOutputStream is used to write to a file via NFS. Normally, any calls to XOutputStream::writeBytes will execute asynchronously then, in that any potential errors might only be reported by later calls to XOutputStream::writeBytes or XOutputStream::closeOutput. If such an output stream shall not be closed immediately after one or more calls to XOutputStream::writeBytes, but the client wants to know as soon as possible whether writing was successful, then XAsyncOutputMonitor::waitForCompletion should be called after the series of calls to XOutputStream::writeBytes.

@since OOo 2.0 */ interface XAsyncOutputMonitor { /** waits for the completion of any previous calls to XOutputStream::writeBytes, and reports potentially pending errors.

Calling this method is potentially expensive (even if the associated XOutputStream represents a local file not accessed via NFS, for example). This method has a similar description to XOutputStream::flush. However, where the semantics of flush are rather vague, waitForCompletion has very specific semantics—it just blocks long enough so that any errors encountered during previous calls to XOutputStream::writeBytes can reliably be reported. It specificially does not guarantee that any data have savely been stored on a stable physical medium, like a hard disk (and it is completely unspecified whether flush should give this guarantee).

@throws com::sun::star::io::IOException if any previous call to XOutputStream::writeBytes encountered such an error, but has not yet reported it (in cases where writeBytes operates asynchronously). */ void waitForCompletion() raises (IOException); }; }; }; }; }; #endif