Êtes-vous un étudiant de l'EPFL à la recherche d'un projet de semestre?
Travaillez avec nous sur des projets en science des données et en visualisation, et déployez votre projet sous forme d'application sur Graph Search.
Concept
Transactional NTFS
Résumé
Transactional NTFS (abbreviated TxF) is a component introduced in Windows Vista and present in later versions of the Microsoft Windows operating system that brings the concept of atomic transactions to the NTFS , allowing Windows application developers to write file-output routines that are guaranteed to either succeed completely or to fail completely.
Major operating system components, including System Restore, Task Scheduler, and Windows Update, rely on TxF for stability. During the development of Windows Vista, WinFS also relied on TxF for storing files.
Due to its complexity and various nuances which developers need to consider as part of application development, Microsoft has deprecated TxF and stated that it may be removed in a future version of Windows. Microsoft has strongly recommended that developers investigate using the alternatives rather than adopting the Transactional NTFS API platform which may not be available in future versions of Windows.
Transactional NTFS allows for files and directories to be created, modified, renamed, and deleted atomically. Using transactions ensures correctness of operation; in a series of file operations (done as a transaction), the operation will be committed if all the operations succeed. In case of any failure, the entire operation will roll back and fail.
Transactional NTFS is implemented on top of the Kernel Transaction Manager, which is a Windows kernel component introduced in Windows Vista that provides transactioning of objects in the kernel. The NTFS file system already supports of low-level operations, such as writing a block of data. Transactional NTFS expands on this capability to include:
Atomic operations on a single file: A common example of this is saving a file from an application; if the application or machine were to crash while writing the file, then only part of the file could be written, possibly resulting in a corrupted file. This would be a very significant problem if a previous version of the file was being over-written, as data would likely be lost.
Source officielle
À propos de ce résultat
Cette page est générée automatiquement et peut contenir des informations qui ne sont pas correctes, complètes, à jour ou pertinentes par rapport à votre recherche. Il en va de même pour toutes les autres pages de ce site. Veillez à vérifier les informations auprès des sources officielles de l'EPFL.