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
Would it be feasible to expose a PUT write stream (or its socket) in a clean way?
Much like get() which provides a read stream, but with put() we can only set a file name. It would be very nice to have something like putStream() which we then can write arbitrarily to.
You could do interesting things with one, such as for instance piping different source files into a single ZIP archive on the FTP server.:
// see: https://github.com/archiverjs/node-archivervararchive=archiver('zip',{zlib: {level: 9}});// .. connect to FTP server and obtain a FTP write stream:varftpWriteStream=ftpClient.putStream('filename.zip'):
archive.pipe(ftpWriteStream);// here!archive.append(someReadStream1,{name: 'file1.txt'});archive.append(someReadStream2,{name: 'file2.txt'});archive.append(someReadStream3,{name: 'file2.txt'});archive.finalize();//...// Done, and one single file created directly on the FTP server// with no need for temp on local.
Hi and thanks for updating this project.
Would it be feasible to expose a PUT write stream (or its socket) in a clean way?
Much like
get()
which provides a read stream, but withput()
we can only set a file name. It would be very nice to have something likeputStream()
which we then can write arbitrarily to.You could do interesting things with one, such as for instance piping different source files into a single ZIP archive on the FTP server.:
Pseudo implementation:
The text was updated successfully, but these errors were encountered: