Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign upclient.seed, stream input #215
Closed
Comments
This comment has been minimized.
This comment has been minimized.
|
me and @feross had this discussion on twitter at some point. the problem with accepting streams as input is that in order to seed you need to be able to "re-read" the input and do random access etc. this means that in order to seed a stream you basically need to load the entire thing into memory (or write it to a tmp file) which kinda defeats the purpose |
This comment has been minimized.
This comment has been minimized.
|
What @mafintosh said :) |
This comment has been minimized.
This comment has been minimized.
|
Ok, thanks! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It looks like streams are used internally in
client.seed().What about allowing a stream as an input?