- java.lang.Object
-
- java.io.FileDescriptor
-
public final class FileDescriptor extends Object
Instances of the file descriptor class serve as an opaque handle to the underlying machine-specific structure representing an open file, an open socket, or another source or sink of bytes. The main practical use for a file descriptor is to create aFileInputStream
orFileOutputStream
to contain it.Applications should not create their own file descriptors.
- Since:
- JDK1.0
- See Also:
FileInputStream
,FileOutputStream
-
-
Field Summary
Fields Modifier and Type Field and Description static FileDescriptor
err
A handle to the standard error stream.static FileDescriptor
in
A handle to the standard input stream.static FileDescriptor
out
A handle to the standard output stream.
-
Constructor Summary
Constructors Constructor and Description FileDescriptor()
Constructs an (invalid) FileDescriptor object.
-
-
-
Field Detail
-
in
public static final FileDescriptor in
A handle to the standard input stream. Usually, this file descriptor is not used directly, but rather via the input stream known asSystem.in
.- See Also:
System.in
-
out
public static final FileDescriptor out
A handle to the standard output stream. Usually, this file descriptor is not used directly, but rather via the output stream known asSystem.out
.- See Also:
System.out
-
err
public static final FileDescriptor err
A handle to the standard error stream. Usually, this file descriptor is not used directly, but rather via the output stream known asSystem.err
.- See Also:
System.err
-
-
Constructor Detail
-
FileDescriptor
public FileDescriptor()
Constructs an (invalid) FileDescriptor object.
-
-
Method Detail
-
valid
public boolean valid()
Tests if this file descriptor object is valid.- Returns:
true
if the file descriptor object represents a valid, open file, socket, or other active I/O connection;false
otherwise.
-
sync
public void sync() throws SyncFailedException
Force all system buffers to synchronize with the underlying device. This method returns after all modified data and attributes of this FileDescriptor have been written to the relevant device(s). In particular, if this FileDescriptor refers to a physical storage medium, such as a file in a file system, sync will not return until all in-memory modified copies of buffers associated with this FileDescriptor have been written to the physical medium. sync is meant to be used by code that requires physical storage (such as a file) to be in a known state For example, a class that provided a simple transaction facility might use sync to ensure that all changes to a file caused by a given transaction were recorded on a storage medium. sync only affects buffers downstream of this FileDescriptor. If any in-memory buffering is being done by the application (for example, by a BufferedOutputStream object), those buffers must be flushed into the FileDescriptor (for example, by invoking OutputStream.flush) before that data will be affected by sync.- Throws:
SyncFailedException
- Thrown when the buffers cannot be flushed, or because the system cannot guarantee that all the buffers have been synchronized with physical media.- Since:
- JDK1.1
-
-
Traduction non disponible
Les API Java ne sont pas encore traduites en français sur l'infobrol. Seule la version anglaise est disponible pour l'instant.
Version en cache
21/11/2024 22:15:30 Cette version de la page est en cache (à la date du 21/11/2024 22:15:30) afin d'accélérer le traitement. Vous pouvez activer le mode utilisateur dans le menu en haut pour afficher la dernère version de la page.Document créé le 29/08/2006, dernière modification le 04/03/2020
Source du document imprimé : https://www.gaudry.be/java-api-rf-java/io/filedescriptor.html
L'infobrol est un site personnel dont le contenu n'engage que moi. Le texte est mis à disposition sous licence CreativeCommons(BY-NC-SA). Plus d'info sur les conditions d'utilisation et sur l'auteur.
Références
Ces références et liens indiquent des documents consultés lors de la rédaction de cette page, ou qui peuvent apporter un complément d'information, mais les auteurs de ces sources ne peuvent être tenus responsables du contenu de cette page.
L'auteur de ce site est seul responsable de la manière dont sont présentés ici les différents concepts, et des libertés qui sont prises avec les ouvrages de référence. N'oubliez pas que vous devez croiser les informations de sources multiples afin de diminuer les risques d'erreurs.