> Why not just have a file that a client reads that lets the client know > of changes to files.
A bit better, but the comment I just made about breaking single-copy
semantics still hold. The point is that merely notifying the client
isn't enough. The server should wait for an acknowledgement to that
notification (which possibly doesn't arrive until after the client has
flushed its updates from the cache).
Sape
