Menu
I want to stream content to clients which is possibly stored in db, which they would save as files.
Obviously res.download would do the job nicely, but none of the response.* functions accept a stream, only file paths.
I had a look at res.download impl and it just sets Content-Disposition header and then a sendfile.
So I could achieve this using this post as a guide. Node.js: pipe stream to response freezes over HTTPS
But it seems I would miss out on all the wrapping aspects that res.send performs.
Am I missing something here or should I just do the pipe and not worry about it - what is best practice here?
Currently creating temp files so I can just use res.download for now.
962
#!/usr/bin/env node const fs = require('fs'); Next, you will create a function below the switch statement called read() with a single parameter: the file path for the file you want to read. This function will create a readable stream from that file and listen for the data event on that stream.
Streams are one of the fundamental concepts of Node. js. Streams are a type of data-handling methods and are used to read or write input into output sequentially. Streams are used to handle reading/writing files or exchanging information in an efficient way.
Make sure that your AJAX request from the client has an appropriate 'responseType' set. for example like
$http({ method :'GET', url : http://url, params:{}, responseType: 'arraybuffer' }).success() You can stream directly to the response object (it is a Stream).
A basic file stream would look something like this.
function(req, res, next) { if(req.url==="somethingorAnother") { res.setHeader("content-type", "some/type"); fs.createReadStream("./toSomeFile").pipe(res); } else { next(); // not our concern, pass along to next middleware function } } This will take care of binding to data and end events.
136
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
