I think the most important case involves a completely opaque temp file. You can perform stream operations on it and share it within a process but have no access to the filesystem specific information (i.e. its filename). Agree or disagree? Dylan Stefan Seefeld wrote:
Matt Doyle wrote:
I didn't know about that, because on win32 there is a problem with deleting open files.
Using the WIN32 call CreateFile specify FILE_ATTRIBUTE_TEMPORARY.
from MSDN -> FILE_ATTRIBUTE_TEMPORARY - A file is being used for temporary storage. File systems avoid writing data back to mass storage if sufficient cache memory is available, because an application deletes a temporary file after a handle is closed. In that case, the system can entirely avoid writing the data. Otherwise, the data is written after the handle is closed.
You still can't delete an open file but you can possibly avoid ever creating the file in the first place..
But then you have to carefully craft the spec, as users may expect to be able to share the file (by name) among processes. There are clearly different use cases for temporary files, so it is important to capture the most important ones.
Regards, Stefan
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost