[Monodevelop-devel] Atomic file write API

[Rafael Teixeira]

It can be done on a additional layer, but not in the framework as that
changes the contract (or perhaps the better term is semantics) of that API
and so it would not have the same results in .NET and in Mono.

Just my two cents,

On Mon, Mar 16, 2009 at 3:46 PM, Levi Bard <
taktaktaktaktaktaktaktaktaktak at gmail.com> wrote:

> >> Shouldn't some of this be pushed down into the mono framework?
> >> Obviously, stuff like restoring from backups is out-of-spec and must
> >> be external, but shouldn't POSIX minutiae be handled by the System.IO
> >> implementation?
> >
> > How could it be fixed? AFAIK the truncate-on-overwrite exists on
> > Windows (though not the need for fsync), which is one reason why
> > Transactional NTFS was added.
>
> Perhaps internally, a write-mode FileStream writes to a temp file,
> then renames on close/dispose (maybe fsync on Flush() where
> necessary/supported).
>
> --
> http://homes.eff.org/~barlow/EconomyOfIdeas.html<http://homes.eff.org/%7Ebarlow/EconomyOfIdeas.html>
> http://www.dreamsongs.com/MobSoftware.html
> http://www.gnu.org/philosophy/shouldbefree.html
> _______________________________________________
> Monodevelop-devel-list mailing list
> Monodevelop-devel-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/monodevelop-devel-list
>



-- 
Rafael "Monoman" Teixeira
---------------------------------------
"I myself am made entirely of flaws, stitched together with good
intentions."
Augusten Burroughs
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ximian.com/pipermail/monodevelop-devel-list/attachments/20090316/d43680db/attachment-0001.html