![]() ![]() Therefore, Microsoft strongly recommends developers investigate using the alternatives rather than adopting the Transactional NTFS API platform which may not be available in future versions of Windows. And I guess I'm not the only one:ĭue to its complexity and various nuances which developers need to consider as part of application development, Microsoft is considering deprecating TxF APIs in a future version of Windows. I confused the concept of the file stream - which I still believe must be a very fundamentally similar concept and likely involved in some way as there can be multiple named and only one unnamed streams for each file - with what is apparently happening with TNTFS. When it is, the file is committed atomically and wholly in one piece. Behaving in a way very like NTFS file streams, Transactional NTFS commits file changes to some alternate cache until the change is guaranteed. The truth is file streams are weird, and they confuse me, but apparently it gets deeper. ![]() ![]() So, I really didn't think I would be researching NTFS this morning, but, thanks mostly to comments below, I learned something. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |