Message 97643 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	brian.curtin
Recipients	brian.curtin, schmir, trent
Date	2010-01-12.18:25:13
SpamBayes Score	2.6790666e-08
Marked as misclassified	No
Message-id	<1263320715.57.0.303020232517.issue2643@psf.upfronthosting.co.za>
In-reply-to

Content
Added the FlushViewOfFile calls, and an msync call to the close method. Not sure how to explicitly test this, if it's possible. Current tests pass on Windows, I'll need to check *NIX when I have the access later today. As for justification, from the UnmapViewOfFile docs[1]: "To minimize the risk of data loss in the event of a power failure or a system crash, applications should explicitly flush modified pages using the FlushViewOfFile function." [1] http://msdn.microsoft.com/en-us/library/aa366882%28VS.85%29.aspx

Added the FlushViewOfFile calls, and an msync call to the close method. Not sure how to explicitly test this, if it's possible. Current tests pass on Windows, I'll need to check *NIX when I have the access later today.

As for justification, from the UnmapViewOfFile docs[1]: "To minimize the risk of data loss in the event of a power failure or a system crash, applications should explicitly flush modified pages using the FlushViewOfFile function."

[1] http://msdn.microsoft.com/en-us/library/aa366882%28VS.85%29.aspx

History
Date	User	Action	Args
2010-01-12 18:25:15	brian.curtin	set	recipients: + brian.curtin, schmir, trent
2010-01-12 18:25:15	brian.curtin	set	messageid: <1263320715.57.0.303020232517.issue2643@psf.upfronthosting.co.za>
2010-01-12 18:25:14	brian.curtin	link	issue2643 messages
2010-01-12 18:25:13	brian.curtin	create