-
Notifications
You must be signed in to change notification settings - Fork 192
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feeding a Builder parts of a file at a time #149
Comments
The |
It's entirely possible I'm wrong about this, but I think that would block up the tokio event loop? |
Ah no yeah that's true, this library is not currently compatible with async I/O |
I'd be willing to put in the effort to make it so, if you've got ideas about how it might be done. |
Hm sure! I haven't put a lot of thought into how this library would support futures and async I/O but my guess is that it'd be relatively low-level. It might be the case that we need to basically just add a new |
That sounds plausible for a first start. It would be nice to get recursive directory adding etc. working with async too if the user opts into it ( |
Seems plausible to me! |
I've had a go at something slightly better (imo) than this initial solution, but I can't quite finish it because I'm slightly confused by what this code (from
In particular, does chaining |
Oh dear that is odd! That can probably be removed now, it may just be something that didn't survive refactorings well |
Is there any news on this? |
On 18 Mar 2019, at 16:23, Boastful Squirrel ***@***.***> wrote:
Is there any news on this?
I gave up on the project that needed this and I’m unlikely to look at it again until Tokio is stabilised.
/j
|
Passing the data in parts would also be necessary to build sparse files. |
it would be pretty handy if async interop was a thing that existed |
Currently, so far as I can tell, it's not possible to stream a file's contents as it becomes available - it is necessary to read an entire file into memory at a time to add it to an archive.
It would be awesome if it were possible to build up an entry's body incrementally, such as in response to filesystem events from tokio.
The text was updated successfully, but these errors were encountered: