https://blogs.technet.microsoft.com/askperf/2007/06/19/basic-printing-architecture/

Printer sharing, information retrieval, and data storage are among the most frequently used network services.  This also means that when something major happens to a print server or file server – lots of people are adversely affected.  Issues with Print Servers and the Print Spooler are very common issues for the Performance team.  So today, we’re going to kick off our series of posts on Printing with an overview of the Windows Printing Architecture and the Print Spooler.

Broken down into basic elements, the Windows printing architecture consists of a print spooler and a set of print drivers.  The print spooler is the primary component of the printing interface.  Most administrators are familiar with the spooler as an executable file (spoolsv.exe) that manages the printing process.  In a default configuration, the spooler is loaded at system startup and continues to run until the operating system is shut down.  The print spooler consists of a set of Microsoft and vendor components that perform the following tasks:

  • Should a print job be handled locally or across a network?
  • Accepting a data stream created by GDI, in conjunction with a printer driver, for output on a particular printer type
  • Spooling the data to a file
  • Selecting the first available physical printer in a logical printer queue
  • Converting a data stream from a spooled format such as EMF to a format that can be sent to the printer hardware (such as PCL)
  • Sending a data stream to printer hardware
  • Maintaining the registry database for spooler components and printer forms

Below is a simplified view of the print spooler components.  When looking at this diagram, if the printer hardware is local to the system, then the “client” and “server” pieces are all on the same machine.

Application – The print application creates a print job by calling Graphics Device Interface (GDI) functions

GDI – GDI includes user-mode and kernel-mode components.  The user-mode component, Microsoft Win32 GDI, is used by Win32 applications that require graphics support.  The kernel-mode component, the graphics engine, exports services and functions that graphics device drivers can use

Winspool.drv – This is the client interface into the spooler.

Spoolsv.exe –  This is the spooler’s API server.  It is implemented as a service when the OS is started

Spoolss.dll – Spoolss.dll acts as a router, determining which print provider to call based on a printer name or handle supplied with each function call.  It then passes the function call to the correct provider.

OK – so let’s discuss print providers.  The print provider is responsible for several functions, including directing print jobs to local or remote print devices and print queue management operations such as starting, stopping and enumerating print queues.  Print providers implement a common set of capabilities that are defined by a set of API functions.  These functions are called by spoolss.dll.  The diagram below illustrates possible flow paths involving different print providers.

The following print providers are supplied by Microsoft in Windows 2000, XP & Windows Server 2003:

localspl.dll – this is the local print provider which handles all print jobs directed to local printers

win32spl.dll – this is the Windows network print provider.  All print jobs directed to remote servers and handled by this provider.  When the job arrives at the remote server it is passed to the server’s local print provider

nwprovau.dll – Novell NetWare print provider

inetpp.dll – HTTP print provider which handles print jobs sent to a URL

Printer manufacturers may also create their own network print providers.

And that brings us to Print Processors.  Print processors are user-mode DLL files that convert the spooled data from a print job into a format that is understood by a print monitor.  When a print job is spooled, the data is contained in a spool file.  The print processor reads the file, performs the conversion on the data stream and writes the converted data to the spooler.  The spooler sends the data to the correct print monitor.  Print processors are associated with printer drivers during driver installation.  The default Print Processor provided with the operating system is winprint.dll.

Lastly, let’s talk about Print Monitors.  These are user-mode DLL’s responsible for directing a print data stream from the spooler to an appropriate port driver.  When we talk about print monitors we are actually referring to two different types of monitor.  First, there is the language monitor which provides a full-duplex communications path between the print spooler and bi-directional printers that are capable of providing software-accessible status information.  In addition, the language monitors add printer control information to the data stream.  It is important to note that Language monitors can be used to add any post spooling processing.  In addition to the Language monitors, we also have Port monitors.  These are responsible for providing a communications path between the user-mode print spooler and the kernel-mode port drivers that access I/O port hardware.  Port monitors are, as the name suggests, responsible for management and configuration of the printer ports on a server.

And that will do it for our look at the Basic Printing Architecture.  In future posts, we will be looking at drivers, troubleshooting and policies.  Until next time …

Additional Resources:

– CC Hameed

Basic Printing Architecture的更多相关文章

  1. Printing Architecture

    Printing Architecture http://www.codeproject.com/Articles/8916/Printing-Architecture     This articl ...

  2. Basic Router Architecture

    from the book principles and practices of interconnection networks  the chapter router architecture ...

  3. Struts 2 Tutorial Basic MVC Architecture

    Model View Controller or MVC as it is popularly called, is a software design pattern for developing ...

  4. Chromium Graphics: Compositor Thread Architecture

    Compositor Thread Architecture <jamesr, enne, vangelis, nduca> @chromium.org Goals The main re ...

  5. Nginx Tutorial #1: Basic Concepts(转)

    add by zhj: 文章写的很好,适合初学者 原文:https://www.netguru.com/codestories/nginx-tutorial-basics-concepts Intro ...

  6. Framework for Graphics Animation and Compositing Operations

    FIELD OF THE DISCLOSURE The subject matter of the present disclosure relates to a framework for hand ...

  7. Command and Query Responsibility Segregation (CQRS) Pattern 命令和查询职责分离(CQRS)模式

    Segregate operations that read data from operations that update data by using separate interfaces. T ...

  8. RNN 入门教程 Part 4 – 实现 RNN-LSTM 和 GRU 模型

    转载 - Recurrent Neural Network Tutorial, Part 4 – Implementing a GRU/LSTM RNN with Python and Theano ...

  9. bluetooth service uuid

    转自:https://www.bluetooth.com/specifications/assigned-numbers/service-discovery service discovery ​​​ ...

随机推荐

  1. JVM之--Java内存结构(第一篇)

    最近在和同事朋友聊天的时候,发现一个很让人思考的问题,很多人总觉得JVM将java和操作系统隔离开来,导致很多人不用熟悉操作系统,甚至不用了解JVM本身即可完全掌握Java这一门技术,其实个人的观点是 ...

  2. MyBatis(3):SQL映射

    前面学习了config.xml,下面就要进入MyBatis的核心SQL映射了,第一篇文章的时候,student.xml里面是这么写的: 1 2 3 4 5 6 7 8 9 10 11 <?xml ...

  3. [LeetCode] Word Search [37]

    题目 Given a 2D board and a word, find if the word exists in the grid. The word can be constructed fro ...

  4. QT5: QApplication, no such file or directory

    In QT5, when I use this: #include<QApplication>, QT tells :no such file or directory, even tho ...

  5. Chapter 7. Dependency Management Basics 依赖管理基础

    This chapter introduces some of the basics of dependency management in Gradle. 7.1. What is dependen ...

  6. Java中字符串内存位置浅析

    前言 之前写过一篇关于JVM内存区域划分的文章,但是昨天接到蚂蚁金服的面试,问到JVM相关的内容,解释一下JVM的内存区域划分,这部分答得还不错,但是后来又问了Java里面String存放的位置,之前 ...

  7. linux中切换用户方式su和su -的区别

    Using su The  su  command allows users to open a terminal window, and from that terminal start a sub ...

  8. MM32Flash读写操作(兼容STM32)

    MM32Flash读写操作(兼容STM32) Flash基础描述 思维导图 编程实现读写操作 主函数结构 #include "delay.h" #include "sys ...

  9. activiti总结

    1.activiti如何修改登录用户名?在哪个数据库里面添加. 2.activiti的启动和部署在http://activiti.org/userguide/index.html#demo.setup ...

  10. 在SPItemEventReceiver中使用BeforeProperties和AfterProperties

    当你利用这些事件时,就很快会发现存在前(同步)后(异步)两种事件.其方法的后缀分别为“ing”(比如,ItemAdding)和“ed”(比如,ItemAdded),分别代表了变更发生前调用和发生后调用 ...