You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 11, 2021. It is now read-only.
The fstream streams interface is more than just a little different from the usual streams2 one. Feels to me like there isn't no base class for processing the stream coming from fstream.Reader so that it fits to fstream.Writer.
What are the aspects to turn attention to: the needed methods to call or event to emit, to implement a API to transform those streams?
I'm thinking of renaming the files on the fly; filtering by the content; regexping the content or encrypting, chaining these processes and combining with the node-tar.
I'm investigating, if anybody has ideas, feel free to give me some directions...
The text was updated successfully, but these errors were encountered:
Honestly, at this point, I'm just kind of procrastinating until I can get npm and node-tar off of these modules, and come up with a better abstraction. Feel free to investigate.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The
fstream
streams interface is more than just a little different from the usual streams2 one. Feels to me like there isn't no base class for processing the stream coming fromfstream.Reader
so that it fits tofstream.Writer
.What are the aspects to turn attention to: the needed methods to call or event to emit, to implement a API to transform those streams?
I'm thinking of renaming the files on the fly; filtering by the content; regexping the content or encrypting, chaining these processes and combining with the node-tar.
I'm investigating, if anybody has ideas, feel free to give me some directions...
The text was updated successfully, but these errors were encountered: