pillarjs/multiparty

README’s reference to busboy and benchmarks is confusing

Closed this issue · 3 comments

binki commented

The linked to benchmarks don’t mention busboy. The README of the npm package mentions temporary files, etc. Does multiparty transparently create temporary files instead of streaming by default or something? Could the README say what causes temporary files to be created?

I think that the README is recommending me use busboy instead, so I will use that then…

Under the hood of busboy is dicer, which is what you see in those benchmarks. Those are the benchmarks linked to from busboy, so you may want to file an issue there to note what dicer means in the benchmarks table.

See also busboy - a faster alternative which may be worth looking into. I agree with @binki about the recommend the library gives. Shall be still moving to Busboy? It's confusing @dougwilson 😕

Use the module that works best for you.