transactions - end of transaction actions

[Aaron Bentley]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Robert Collins wrote:
| accordance with the above ordering rule]. One decision we need to make
| is whether writes can be globbed together - i.e. if I ask for something
| to be written that affects files X, then Y, then X again, can the system
| write both setsof data to X, and then the one to Y? I think that this
| violates the domain ordering constraints in the background section
| above, and we should say that the transaction must not allow that to
| happen.

I would add, "absent specific grouping instructions."  For example, if
you delayed writes to inventory storage until all text storage updates
were complete, you'd be able to do the text storage updates in any order
you liked.

Not that we should necessarily do this, but it does seem possible.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFD1YnQ0F+nu1YWqI0RAhmGAJ0e90B5TZJUVTq8nb++yUbGbZacrgCfclk8
ujFVuczDsas7n73c94Vx3yo=
=ZCCI
-----END PGP SIGNATURE-----