While you are thinking about this stuff, keep in mind that some OSes such as win32 have the ability to open a file as temporary and will automatically delete it when the last handle is closed. It would be nice if that could be exploited by whatever interface is decided upon. joe
I didn't know about that, because on win32 there is a problem with deleting open files. On unix systems (probably most or all of them) you can delete file and when last handle is closed kernel automatically removes file - it's great solution. Anyway, same people on unix (in same cases) first open temp file, then remove it and then use it - no one could do anything with your file. Tom On Fri, 9 Sep 2005, Greer, Joe wrote:
While you are thinking about this stuff, keep in mind that some OSes such as win32 have the ability to open a file as temporary and will automatically delete it when the last handle is closed. It would be nice if that could be exploited by whatever interface is decided upon.
joe
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
From: at@tru.pl
I didn't know about that, because on win32 there is a problem with deleting open files. On unix systems (probably most or all of them) you can delete file and when last handle is closed kernel automatically removes file - it's great solution.
Anyway, same people on unix (in same cases) first open temp file, then remove it and then use it - no one could do anything with your file.
Unlinking a file after opening it is a good way to ensure no other user can manipulate the file. However, short of duplicating file handles for other processes, one can't share the file after unlinking it. The pathname is no longer valid, and that's how one accesses a file with Boost.Filesystem. -- Rob Stewart stewart@sig.com Software Engineer http://www.sig.com Susquehanna International Group, LLP using std::disclaimer;
participants (3)
-
at＠tru.pl -
Greer, Joe -
Rob Stewart