[cups.development] [RFE] STR #2878: Standby/failover printer inside a CLASS

[Dominik Kubla]

DO NOT REPLY TO THIS MESSAGE.  INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.

[STR New]

I think a more general approach would be even better: Introduce a per-class
scheduling policy with a global default. At least four possible settings
come to mind:

* round-robin
* first
* parallel
* failover

"Round-robin" should be the default.

"First" would alway use the server who offered the printer first until it
becomes unavailable. That would make it easier to preserve the order of
print jobs, which is some times an important issue.

"Parallel" would issue the job to every printer in the class. One example
would be to pair a real printer with a digital archival system.

"Failover" would require one or more servers offering the printer be
designated as the primary server(s) for that printer.

Further possibilites could be

* nearest
* load

but these would require the client to have additional informations like
hop count to the server, server performance or server load. So they might
not be possible to implement

Link: http://www.cups.org/str.php?L2878
Version:  -feature