Skip to content
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

Zip in channel #11

Closed
wants to merge 2 commits into from
Closed

Conversation

brendanlong
Copy link
Contributor

@brendanlong brendanlong commented Jan 9, 2018

This lets us read zip files that aren't on the file system.

In particular, I want to be able to unzip files that I'm already holding in memory, and pushing them through a pipe is better than having to write to a temp file. Ideally I wouldn't need an in_channel at all, but taking a string as an input would be a lot more changes.

This lets people read files that aren't necessarily on the file
system (for example, files being streamed over the network, or
files sent through a pipe).
@brendanlong
Copy link
Contributor Author

Actually, this probably isn't that useful since you can't seek a pipe or socket :\

@xavierleroy
Copy link
Owner

Thanks for the proposal. As you wrote it's probably not enough for what you want to achieve. A case could be made for refactoring this library on top of abstract I/O channels that support both files and in-memory data (strings and bytes, but also Buffer.t and bigarrays, see #7). That's significant work, though.

@brendanlong
Copy link
Contributor Author

Hmm yeah I might look into that at some point :)

@brendanlong brendanlong deleted the zip_in_channel branch January 16, 2018 15:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants