Backend appears to closedown before myraster filter sends output

[Paul Newall]

The backend is dnssd
Of course you could be right that it's the printer timing out.
I have a working fix for the problem now, which is to send a harmless command to the printer every 15 seconds during the periods when the filter is busy and so is not sending data to the printer.

Paul

> More than likely it is the printer that has timed out.
>
> What backend are you using?
>
> On Oct 1, 2010, at 3:45 PM, Paul Newall wrote:
>
> > My raster filter works OK with small pages.
> > But when I print large pages at high resolution, which take longer to =
> RIP (more than 30 seconds), the filter output does not seem to get sent =
> to the (network) printer.
> > I guess the backend has timed out before I send any data.
> > Does this sound likely?
> > How could I confirm that is the problem?
> > Can I extend the timeout time for the backend?
> >=20
> > _______________________________________________
> > cups-dev mailing list
> > cups-dev at easysw.com
> > http://lists.easysw.com/mailman/listinfo/cups-dev
>
> ________________________________________________________________________
> Michael Sweet, Senior Printing System Engineer, PWG Chair
>
>
>
>