I played with DAOS and encrypted mail on a test server and found the following.
User A sends an encrypted mail to User B. The mail has an attachment.
In the DAOS Dir I can see now 2 NLO files. One for the document stored in the senders sent view and the other one for the document in the inbox of User B.
Now User B sends an encrypted mail to User A and attaches the same bitlike file from the filesystem.
Again 2 NLO files are created in the DAOS Dir.
I’m asking the DAOS Team. Does DAOS work as designed or is there sonething weired going on.
I’ve wrote about this in my blog as well. DAOS – Encrypted mail | eknori.de
Subject: Encryption and the number of NLO’s
Remember that DAOS only externalizes objects “as they exist” inside the NSF’s. It consolidates references to the content if it happens to exist in more than one place. So, the fact that “sharing” does not happen in this scenario is not any sort of failure of the DAOS mechanism, it simply means the users did not receive the same output for a given input. You have no more (or less) disk usage than you had without DAOS but you still get the important large benefit of being able to use a separate device to store this attachment, and the ability to incrementally back it up.
Subject: Yes, this is behaving correctly.
I would go into details, but Nathan has already provided all of them in a response to your blog post.
Subject: Thanks for feedback