Not sure if this has anything to do with torrent-stream, but I've made a little test app that uses the engine to process torrent search results. I had a front end button that signals the first get route, which triggers disconnect and destroy the stream.
Two issues. One is I frequently end up with what seems like multiple streams (double or triple console.log statements), and when attempting to access the new route aka the next link in the filtered search results, I get an error: can't set headers after they are sent.
Any help would be appreciated, either way thank you for this, it has been great to work with and learn some node/express.
Not sure if this has anything to do with torrent-stream, but I've made a little test app that uses the engine to process torrent search results. I had a front end button that signals the first get route, which triggers disconnect and destroy the stream.
Two issues. One is I frequently end up with what seems like multiple streams (double or triple console.log statements), and when attempting to access the new route aka the next link in the filtered search results, I get an error: can't set headers after they are sent.
Any help would be appreciated, either way thank you for this, it has been great to work with and learn some node/express.