Closed rexxars closed 9 years ago
Solved in 4f00f4fab255826d0520f2baedfbcd75f765c3c0 and released as 1.0.6. I didn't see any reason to use an option for this - it seemed like the reasonable thing to do, so it simply checks if the flush method exists on the response and calls it after a write.
The
compression
middleware for express (and probably others as well) causes some issues with the library, since it'll wait for a certain amount of data before sending it downstream. Documented here.Adding an option that would enable explicit flushing after each write would be a good thing, along with documenting both the option and the problem in the README.