Re: [boost] [compond_file_binary] Gauging interest in a possible library submission.

The MS implementation achieves this using the transactional mechanisms, which moves the responsibility for making it concurrency safe into user land. Essentially every write creates a new subtree (stream), which then is made current by a single atomic write operation, invalidating the previous version of the data.

This sounds right. Before I never used compound files in transactional mode, so additional investigations are needed. -- View this message in context: http://boost.2283326.n4.nabble.com/compond-file-binary-Gauging-interest-in-a... Sent from the Boost - Dev mailing list archive at Nabble.com.