rastertopcl creating very large (> 2 GB) files

Anonymous anonymous at easysw.com
Mon Sep 26 14:26:42 PDT 2005


> > > Does "socket" stream, and if so is it faster
> > > at transfering data than IPP?
> >
> > IPP can stream the print data, however the current backend does not
> > stream data since HP's IPP implementation does not support it.
> >
> > The socket backend streams print data to the printer and is generally
> > the fastest way to print.
>
> OK.  I'll try using the socket backend. . .
>
> I'm confused about what the IPP backend was doing if it wasn't streaming.  Was it just copying so slowly that the printer decided (it's set to "intelligently" decide whether to wait for the entire file to be transferred before it starts) to print before receiving the 6 GB PJL/HPGL2 temporary file, which was able to be printed before it filled up a 4.8 GB hard drive?  The printer would take tens of seconds to print a single line for this test--it usually spits out an ~4'x8' poster in a few minutes, but it took hours for this print to finish using the IPP backend on CUPS.
>
> Anyway, thanks for the information!
>
> Well, I tried socket:, and I get a "network host 'hp-5000' is busy; will retry in 30 seconds." message from lpstat -p. . .  I guess we're stuck with the IPP backend for now. . .





More information about the cups mailing list