Hi Valient, time ago you spoke about making code more portable. Time ago (year actually) I start writing a port to the Windows world. The code is running but have a lot of problems as I tried to change encfs code as less as possible but the Windows behaviour is quite different than Unix (fuse) one. The result is quite terrible having many problems. The better way would be to change encfs to be more Windows... or more portable extending portable area to Windows. Some examples: - When a file is opened on Windows a lot of flags are passed like permissions (acl), locking flags, filesystem flags and others. The idea would be to change encfs to change open interface to accept an abstract structure with all flags. To create the real file than encfs would call another function which understand this structure and open the file for you; - Windows (Dokan actually) can pass context pointer directly so there's no need to call fuse_get_context, I would change functions to accept a pointer context (I think most function actually read the context pointer).
I'm quite busy at the moment, however... can you think you can accept such changes? Frediano ------------------------------------------------------------------------------ Sponsored by Intel(R) XDK Develop, test and display web and hybrid apps with a single code base. Download it for free now! http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk _______________________________________________ Encfs-users mailing list Encfs-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/encfs-users
