happend to be a bad idea. Well, it is not that bad, but it does not save anything, since I want to have transformation functions to be replaceble at remount time, but having to rebuild inode cache for this is not a good idea.

So I will have a list of destination IDs attached to inode (and thus subsequently to transactions), and maybe eventually there will be ability to attach filtes to store some objects with one set of transformation functions (and thus amount of copies) and other objects with another one. Like having all '*.txt' files stored with sha1(name) and sha256(name) IDs while '*.sql' with only one copy. But I will rest this for some future.

We are getting closer to have a write support in new POHMELFS connected to elliptics network, but yet there is a fair amount of work even for this rather simple task.

Stay tuned!