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. 新建maven工程时pom.xml报错

    新建maven工程时,pom.xml报错:第一行报如下错误:multiple annotations found at this line后添加org.eclipse.m2e相关的plugin配置后, ...

  2. ASP.NET MVC框架开发系列课程 (webcast视频下载)

    课程讲师: 赵劼 MSDN特邀讲师 赵劼(网名“老赵”.英文名“Jeffrey Zhao”,技术博客为http://jeffreyzhao.cnblogs.com),微软最有价值专家(ASP.NET ...

  3. POJ 3233 Matrix Power Series (矩阵+二分+二分)

    题目地址:http://poj.org/problem?id=3233 题意:给你一个矩阵A,让你求A+A^2+……+A^k模p的矩阵值 题解:我们知道求A^n我们可以用二分-矩阵快速幂来求,而 当k ...

  4. 动态规划+滚动数组 -- POJ 1159 Palindrome

    给一字符串,问最少加几个字符能够让它成为回文串. 比方 Ab3bd 最少须要两个字符能够成为回文串 dAb3bAd 思路: 动态规划 DP[i][j] 意味着从 i 到 j 这段字符变为回文串最少要几 ...

  5. shell 脚本实现的守护进程

    转自:http://blog.csdn.net/cybertan/article/details/3235722 转自:http://blog.sina.com.cn/s/blog_4c451e0e0 ...

  6. ASP.NET-FineUI开发实践-2

    FineUI好处之一在于No JS,这里的No JS并不是不使用JS,JS对于ASP.Net是必不可少的,只是FineUI把大部分JS封装,如果想用,后台提供了很多方法返回JS,Get...Refer ...

  7. 制作ado开发辅助工具类SqlHelper

    public static class SqlHelper { //通过配置文件获取连接字符创 private static readonly string constr = Configuratio ...

  8. oracle 中如何定位重要(消耗资源多)的SQL【转】

    1.查看值得怀疑的SQL )||'%'load, s.executions executes, p.sql_text from(select address, disk_reads, executio ...

  9. VS专案项目无法生成pdb文件解决办法

    在系统盘里找到该项目对应的dll文件(我的是在C:\Windows\Microsoft.NET\assembly\GAC_MSIL目录下),删除该dll后重新生成项目即可.

  10. 使用poi3.9的jar输出excel

    // 取得模板文件存放的路径 ReadFilePath = ServletActionContext.getServletContext().getRealPath(ExcelTemplateFile ...