I've been looking to use this library with file providers that are purely asynchronous and was wondering what you thought about having overrides for methods touching the EncFSFileProvider that were asynchronous (via promises/callbacks/etc). I'm really interested in using this library to interact with network-backed files over WebDAV/Google Drive/etc, and it's difficult to create a good user experience with synchronous network requests. It's also difficult to use the library from GWT where synchronous XHRs are not viable.
It looks like marcoschulte has forked the project and done this for selective methods already (see getFile/etc: https://bitbucket.org/marcoschulte/encfs-gwt/src/cef3be1dd29b599a42832e5030565a4a17a5b45f/src/main/java/de/voot/encfsgwt/shared/mrpdaemon/EncFSVolume.java?at=develop), however I'd like to use the mainline project.
I'd be willing to contribute the patches for this, if needed. Thoughts?
I've been looking to use this library with file providers that are purely asynchronous and was wondering what you thought about having overrides for methods touching the EncFSFileProvider that were asynchronous (via promises/callbacks/etc). I'm really interested in using this library to interact with network-backed files over WebDAV/Google Drive/etc, and it's difficult to create a good user experience with synchronous network requests. It's also difficult to use the library from GWT where synchronous XHRs are not viable.
It looks like marcoschulte has forked the project and done this for selective methods already (see getFile/etc: https://bitbucket.org/marcoschulte/encfs-gwt/src/cef3be1dd29b599a42832e5030565a4a17a5b45f/src/main/java/de/voot/encfsgwt/shared/mrpdaemon/EncFSVolume.java?at=develop), however I'd like to use the mainline project.
I'd be willing to contribute the patches for this, if needed. Thoughts?