Of course it can’t. If you need to make a PUT (1 PUT) to the network and you don’t, your data is not on the network. It’s that simple. His solution is to avoid writing the file…
And eventually (say once every x hours) once you’ve modified a bunch of small files, “consolidate” those and pack the changes in the minimal number of new PUTs. If you edited just 1 file you’ll still spend one Safecoin to pay for the PUT and during this interval if you try to access your data from elsewhere of course you won’t see the new files.
So just as I said if you need to fix a typo on your blog, you’d better update on schedule and in batches and for data that need concurrent access to recent files from multiple locations, no workaround will work well unless your clients can exchange cached content between them using some sort of shared temp store (such as Dropbox ;-)).
Which brings me back to my earlier claim that it’s more productive to focus on read-mostly workloads rather than devise these complex schemes to turn MaidSafe into something it’s not supposed to do (at least in not in v1).
Related to this, not so long ago there was another nebulous idea to boot corporate systems from SAFE, without any consideration how most systems (including file servers) require fairly frequent updates to shared data or otherwise they can’t work in a meaningful way or risk data loss.