![]() ![]() not preventing use of platform-specific I think we need to get clarity on the shared concepts as opposed to terminology.Įven though in terms of names, the Windows EAs (extended attributes) seem to be a closer fit, conceptually, ADS seem to be the equivalent of the Unix-world extended attributes, i.e. I think a platform-neutral abstraction along the lines you've proposed would be beneficial, and seems possible at least in principle, given that what the platform-specific features share in the abstract is the ability to attach name-value pairs of arbitrary data to file-system items - but there are many details to be hashed out, and it'll be a challenge to find the right balance between focusing on shared, platform-neutral functionality vs. ![]() What's your take on which direction this proposal might take? NET APIs for ADS (NTFS alternate data streams) yet, though PowerShell's cmdlets do support them. There are even recent developments like Linux NFS support for xattr: User Xattr Support Finally Landing For NFS In Linux 5.9 To cite one comment: " I've been wanting this for years!" ) Proposed APIĪs extension to yes, as far as I'm aware there are no. Platform/file system support seems to be good. Internet Explorer seems to store the "downloaded from Internet" information there, Antivirus vendors store scan information, Dropbox used those properties in the past as well - there definitely are use cases.Įxtended file attributes are a lightweight, cross-platform way of storing file metadata that cannot be tinkered with (at least not easily) by the user. My use case specifically is storing an ID for files that is not visible for the user but links those files to external cloud sources those files were generated (and need to be updated) from. Windows documentation (?): ( $EA and $EA_INFORMATION) ![]() On *nix based systems they are called xattr, on Windows E xtended A ttributes ( EA). What are extended file attributes? Citation from the Wikipedia article:Įxtended file attributes are file system features that enable users to associate computer files with metadata not interpreted by the filesystem, whereas regular attributes have a purpose strictly defined by the filesystem (such as permissions or records of creation and modification times). The API currently lacks support to create, read, update and delete "extended file attributes". ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |