Hi,
In a normal setup, files are activated and published out in full. The system just knows a node is changed, and activates it accordingly, without the context of what has changed.
So when using Tar storage, this is an ideal scenario for a shared datastore, so that author and publish access the same file, so there is no copying.once you turn on binary less replication,
As you are using Mongo, then the file is shared in author only, and must be replicated out to the publish servers. This is fine unless you deal with very large files.
I think this would be good to qualify with Customer Care or post in the sticky above for a feature request
Mark