In this chapter, we begin building a basic IPP request library in .NET using the C# language. Up to this point in the book, I have recommended using the Microsoft print subsystem (System.Drawing.Printing) framework if you are on Windows printing to install local printers or printers shared off a print server. There are many good reasons for doing this – support, stability, and built-in data translation are but a few that come to mind. However, as you might imagine, not all usability requirements fall into this scenario. For instance, you might want to use a printer not installed on your computer. Maybe you want a library you could plug into existing code bases to print, and the printer is not known or defined for Windows yet. Perhaps you have a requirement to send documents to arbitrary IPP/IPPS printers in your network depending on programmatic states. Whatever your intention or requirements, this chapter will investigate how to develop a solution to fit this scenario. If you are planning to develop or need to support production code using IPP/IPPS print, I would highly recommend you implement the CUPS port to Windows provided by the PWG. However, if you are just interested in learning about IPP in more detail, there is no better instruction into how a system works than participating in the actual construction of the system. This is true for both developers and those wanting to learn more about how the system works – I hope this chapter is instructive for both developers and system engineers.

错误:搜索内容不能为空,请输入英文关键词
错误:关键词超出字数限制,请精简
高级检索

IPP Standards Print

  • John Marion

摘要

In this chapter, we begin building a basic IPP request library in .NET using the C# language. Up to this point in the book, I have recommended using the Microsoft print subsystem (System.Drawing.Printing) framework if you are on Windows printing to install local printers or printers shared off a print server. There are many good reasons for doing this – support, stability, and built-in data translation are but a few that come to mind. However, as you might imagine, not all usability requirements fall into this scenario. For instance, you might want to use a printer not installed on your computer. Maybe you want a library you could plug into existing code bases to print, and the printer is not known or defined for Windows yet. Perhaps you have a requirement to send documents to arbitrary IPP/IPPS printers in your network depending on programmatic states. Whatever your intention or requirements, this chapter will investigate how to develop a solution to fit this scenario. If you are planning to develop or need to support production code using IPP/IPPS print, I would highly recommend you implement the CUPS port to Windows provided by the PWG. However, if you are just interested in learning about IPP in more detail, there is no better instruction into how a system works than participating in the actual construction of the system. This is true for both developers and those wanting to learn more about how the system works – I hope this chapter is instructive for both developers and system engineers.