[cups.general] Difference CUPS <-> Windows Spooler

[Stefan Monnier]

> With CUPS, an application will send either a PDF or PostScript file
> which is spooled in a temporary file (/var/spool/cups/dNNNNN-NNN)
> before printing - that is the main source of delay with large print
> files.

And this delay seems unrelated to the location and coupling of the
printer driver.  The issue is that CUPS decides to wait until
(/var/spool/cups/dNNNNN-NNN) is fully written before passing it to the
next filter instead of piping it directly while it gets written.

Is cupsd going to ever get the equivalent of gcc's "-pipe" option?


        Stefan