59 lines
3.6 KiB
HTML
59 lines
3.6 KiB
HTML
|
<?xml version="1.0" encoding="UTF-8"?>
|
||
|
|
<!DOCTYPE html
|
||
|
|
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
||
|
|
<html lang="en-us" xml:lang="en-us">
|
||
|
|
<head>
|
||
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
||
|
|
<meta name="security" content="public" />
|
||
|
|
<meta name="Robots" content="index,follow" />
|
||
|
|
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
|
||
|
|
<meta name="DC.Type" content="task" />
|
||
|
|
<meta name="DC.Title" content="Using forced buffered data APIs" />
|
||
|
|
<meta name="abstract" content="Read about using the QHFFRCSF or fscync() APIs to write optical file data to nonvolatile media while writing to optical media." />
|
||
|
|
<meta name="description" content="Read about using the QHFFRCSF or fscync() APIs to write optical file data to nonvolatile media while writing to optical media." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="tipsandtechniques.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2000, 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2000, 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="bufferdata" />
|
||
|
|
<meta name="DC.Language" content="en-us" />
|
||
|
|
<!-- All rights reserved. Licensed Materials Property of IBM -->
|
||
|
|
<!-- US Government Users Restricted Rights -->
|
||
|
|
<!-- Use, duplication or disclosure restricted by -->
|
||
|
|
<!-- GSA ADP Schedule Contract with IBM Corp. -->
|
||
|
|
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
|
||
|
|
<link rel="stylesheet" type="text/css" href="./ic.css" />
|
||
|
|
<title>Using forced buffered data APIs</title>
|
||
|
|
</head>
|
||
|
|
<body id="bufferdata"><a name="bufferdata"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Using forced buffered data APIs</h1>
|
||
|
|
<div><p>Read about using the QHFFRCSF or fscync() APIs to write optical
|
||
|
|
file data to nonvolatile media while writing to optical media.</p>
|
||
|
|
<div class="p"><p>When creating or updating optical files, the data is not guaranteed
|
||
|
|
to exist on optical disk until the file is successfully closed. Optical file
|
||
|
|
data can, however, be synchronously written to nonvolatile storage using either
|
||
|
|
the HFS API Force Buffered Data (QHFFRCSF) or the fsync() UNIX-type API. The
|
||
|
|
type of nonvolatile storage is different depending on the optical media format. </p>
|
||
|
|
<p>For
|
||
|
|
the High Performance Optical File System (HPOFS), all file data will be written
|
||
|
|
to the internal disk storage. The data can then be recovered through a held
|
||
|
|
optical file if a power loss or other unexpected error occurred which prevented
|
||
|
|
the file from being closed.</p>
|
||
|
|
<p>For Universal Disk Format (UDF), all file
|
||
|
|
data will be written to the optical disk when a force operation is issued.
|
||
|
|
No recovery is required if a power loss or other unexpected error occurs,
|
||
|
|
which prevents the file from being closed. However, if write operations are
|
||
|
|
issued after the data is forced and the close operation is never successful,
|
||
|
|
the file data is unpredictable. Because the write operations that follow the
|
||
|
|
force operation are asynchronous, the data might not be written
|
||
|
|
to the optical disc.</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="tipsandtechniques.htm" title="The following techniques are often helpful in designing custom optical programs for your business.">Tips: Optical programming</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|