[Printing-architecture] 3.6 Use Model 5: Desktop Office Printing

[Printing-architecture] 3.6 Use Model 5: Desktop Office Printing

[Till Kamppeter]

here it is.

    Till


3.6 Use Model 5: Desktop Office Printing

Document from an application is printed on a printer shared by 3-5 
workplaces

Example Use Model:

X is working in an office room with three other employees. Everone has a 
PC and there is a color inkjet (for the few color printouts needed) and 
a small laser (for the stuff which is confidential and should not leave 
this room) in the room. X wants to print some color and black-and-white 
documents with different quality requirements on the printers in his 
room. It should by all means be avoided that one of the documents comes 
out on the central printer in the hallway.

Details:

1. X creates a confidental document containing color photos in an office 
application on his desktop PC. He wants to print it and therefore he 
chooses "File"/"Print" in his application program.

2. The application program contacts the local spooler on X's PC to ask 
for the available printers and there basic capabilities as Description, 
Location, bw/color, photo-capable, ...

3. The local spooler communicates with the other print spoolers on the 
local network to exchange the information of the available printers.

3.1 All machines hosting a print queue and having it configured for 
being shared (print servers) broadcast a list of their print queue names 
together with the server's IP address.

In our case Y's machine has the inkjet on its USB and Z's machine the 
laser on its parallel port. Also the server in the server room for the 
printer in the hallway (connected via ethernet adapter) sends broadcasts.

3.2 All other spoolers are listening for these broadcasts and so get the 
  queue list from every server.

So the spooler on X´s machine gets "inkjet on PC Y", "laser on PC Z", 
"hallway_printer on central_server".

3.3 The spooler knows about the existence of all queues now and so it 
can ask all servers for the basic capabilities. The server return the 
following info:

Y: inkjet  6-ink photo color printer,  room of W, X, Y, and Z
Z: laser   desktop bw laser printer, 10 p/min,  room of W, X, Y, and Z
central_server:  workgroup color laser 50 p/min,  hallway 1st floor

4. This the local spooler sends as answer to the request of the 
application program the information shown in 3.3.

5. The application pops up the printing dialog with the printer menu. X 
reads what printers are available.

6. X chooses the inkjet as it is the photo-capable color printer and it 
is in his room, so that noone in the hallway will see this confidential 
document.

7. The photos have to come out in the best possible quality, as the 
document is an application for some big business. So X cklicks on 
"Properties" to adjust the quality. The application requests the full 
capabilities of the inkjet from the local spooler.

8. X asks W, who is a student working in the company, to put 
high-quality inkjet paper into the one tray of the inkjet.

9. The local spooler polls the full capabilities of the inkjet (the 
user-settable options, the non-printable margins, the resolution, ...) 
from the spooler on Y's PC.

10 Y's PC answers the required info back and X's spooler passes it on to 
the application program.

11. The option dialog pops up and X chooses "High Quality" in the 
"Quality" option, "Photos and text" in the "Document type" option and 
"High quality inkjet paper" in the "Media Type" option. X does not mark 
"Notification on end of job", as he can see the printer (otherwise he 
would subscribe to end-of-job notification).

12. X clicks OK for the options and the "Print" in the printing dialog.

13. The PostScript generator of the application resizes the photos from 
the camera's 14 MP to the 600 dpi of the inkjet printer and builds the 
PostScript file of the documents with all fonts and photos embedded. It 
stops with an error message popup if elements of the document fall in 
the unprintable border, asking the user whether he wants to print 
anyway. X says "No", corrects the offending part and prints again.

14. The application sends the PostScript file with all options in the 
job ticket to the local spooler.

15. The local spooler passes the data on to the spooler on Y's machine

16. The spooler on Y's machine reads the job ticket and calls renderer 
and driver appropriately to generate the data in the inkjet's native 
language.

17. The spooler sends the data to the USB and the printer prints.

18. Sees the paper coming out and picks up the excellent quality printout.

Re: [Printing-architecture] 3.6 Use Model 5: Desktop Office Printing

[Till Kamppeter]

I have added some things which I forgot.

    Till


Till Kamppeter wrote:
> here it is.
> 
>    Till
> 
> 
> 3.6 Use Model 5: Desktop Office Printing
> 
> Document from an application is printed on a printer shared by 3-5 
> workplaces
> 
> Example Use Model:
> 
> X is working in an office room with three other employees. Everone has a 
> PC and there is a color inkjet (for the few color printouts needed) and 
> a small laser (for the stuff which is confidential and should not leave 
> this room) in the room. X wants to print some color and black-and-white 
> documents with different quality requirements on the printers in his 
> room. It should by all means be avoided that one of the documents comes 
> out on the central printer in the hallway.
> 
> Details:
> 
> 1. X creates a confidental document containing color photos in an office 
> application on his desktop PC. He wants to print it and therefore he 
> chooses "File"/"Print" in his application program.
> 
> 2. The application program contacts the local spooler on X's PC to ask 
> for the available printers and there basic capabilities as Description, 
> Location, bw/color, photo-capable, ...
> 
> 3. The local spooler communicates with the other print spoolers on the 
> local network to exchange the information of the available printers.
> 
> 3.1 All machines hosting a print queue and having it configured for 
> being shared (print servers) broadcast a list of their print queue names 
> together with the server's IP address.

The broadcasts can go to a whole LAN but also to selected machines.

> 
> In our case Y's machine has the inkjet on its USB and Z's machine the 
> laser on its parallel port. Also the server in the server room for the 
> printer in the hallway (connected via ethernet adapter) sends broadcasts.
> 

Y's and Z's boxes broadcast only to the machines of W, X, Y, and Z, the 
server in the server room broadcasts to the whole LAN. In addition, Y's 
and Z's boxes only accept jobs from W's, X's, Y's, and Z's machines. 
This way one avoids that the printers in our room print jobs from other 
rooms, so that

- Noone from another department wastes our department's ink, toner, and 
paper

- Noone comes in for picking up a print job disturbing W, X, Y, and Z 
during there work.

- Noone from other rooms sees the confidential documents when he picks 
up his jobs

> 3.2 All other spoolers are listening for these broadcasts and so get the 
>  queue list from every server.
> 
> So the spooler on X´s machine gets "inkjet on PC Y", "laser on PC Z", 
> "hallway_printer on central_server".
> 
> 3.3 The spooler knows about the existence of all queues now and so it 
> can ask all servers for the basic capabilities. The server return the 
> following info:
> 
> Y: inkjet  6-ink photo color printer,  room of W, X, Y, and Z
> Z: laser   desktop bw laser printer, 10 p/min,  room of W, X, Y, and Z
> central_server:  workgroup color laser 50 p/min,  hallway 1st floor
> 
> 4. This the local spooler sends as answer to the request of the 
> application program the information shown in 3.3.
> 
> 5. The application pops up the printing dialog with the printer menu. X 
> reads what printers are available.
> 
> 6. X chooses the inkjet as it is the photo-capable color printer and it 
> is in his room, so that noone in the hallway will see this confidential 
> document.
> 
> 7. The photos have to come out in the best possible quality, as the 
> document is an application for some big business. So X cklicks on 
> "Properties" to adjust the quality. The application requests the full 
> capabilities of the inkjet from the local spooler.
> 
> 8. X asks W, who is a student working in the company, to put 
> high-quality inkjet paper into the one tray of the inkjet.
> 
> 9. The local spooler polls the full capabilities of the inkjet (the 
> user-settable options, the non-printable margins, the resolution, ...) 
> from the spooler on Y's PC.
> 
> 10 Y's PC answers the required info back and X's spooler passes it on to 
> the application program.
> 
> 11. The option dialog pops up and X chooses "High Quality" in the 
> "Quality" option, "Photos and text" in the "Document type" option and 
> "High quality inkjet paper" in the "Media Type" option. X does not mark 
> "Notification on end of job", as he can see the printer (otherwise he 
> would subscribe to end-of-job notification).
> 
> 12. X clicks OK for the options and the "Print" in the printing dialog.
> 
> 13. The PostScript generator of the application resizes the photos from 
> the camera's 14 MP to the 600 dpi of the inkjet printer and builds the 
> PostScript file of the documents with all fonts and photos embedded. It 
> stops with an error message popup if elements of the document fall in 
> the unprintable border, asking the user whether he wants to print 
> anyway. X says "No", corrects the offending part and prints again.
> 
> 14. The application sends the PostScript file with all options in the 
> job ticket to the local spooler.
> 
> 15. The local spooler passes the data on to the spooler on Y's machine
> 
> 16. The spooler on Y's machine reads the job ticket and calls renderer 
> and driver appropriately to generate the data in the inkjet's native 
> language.
> 
> 17. The spooler sends the data to the USB and the printer prints.
> 
> 18. Sees the paper coming out and picks up the excellent quality printout.
>