Web Services for Devices Install: Printers & Scanners Mike Fenelon Software Developer Digital Documents, Platform and Solutions Team MFenelon @ microsoft. com Microsoft Corporation
Printing with Web Services for Devices
Printer Installation Step-By-Step Spooler Pn. P-Printer Class Installer WSD Port Monitor 8 8 1 11 11 Function Discovery (FD) Print Device PDO 9 9 44 77 Print Service FDO IPBus. Enumerator 6 6 5 5 10 User-Mode Enabled Bus Enumerator (UMBus) 3 WS-Discovery Provider 2
Step 1 - WSD Port Monitor Initialization Spooler starts up Spooler WSD Port Monitor 1 Function Discovery (FD) WSD Port Monitor (WSDMon) queries FD for all existing WSD print devices and creates the appropriate ports Any new devices found while the spooler wasn’t running will also kick off Pn. P installation for the Print Object (Step 9) WSDMon will also register for notifications on the correct FD category to receive future device notifications
Steps 2 & 3 – Printer Announcement and Discovery Function Discovery (FD) 3 WS-Discovery Provider 2 Printer announces presence on the network by a WS-Discovery “Hello” message or responds to a Probe message from user opening Computers & Devices WS-Discovery provider recognizes the device and publishes it to Function Discovery (FD) Device Instance in FD contains all the basic device Metadata Device enabled for install if it contains Pn. P-X related metadata
Steps 4 & 5 – Notification from FD and Devnode Creation Function Discovery (FD) 4 IPBus. Enumerator 5 User-Mode Enabled Bus Enumerator (UMBus) From Within Computers & Devices the User adds/installs discovered device to Association Database IPBus. Enum gets a notification of the newly associated Network Device IPBus. Enum reads data from the new instance and uses the COM interface to the User. Mode Enabled Bus Enumerator (UMBus) to tell UMBus to create a new WS Print Service Dev. Node
Step 6 – Create Printer Service Devnode Scan Service FDO 6 User-Mode Enabled Bus Enumerator (UMBus) UMBus creates a File Device Object (FDO) for the WSbased Printer Service This FDO has a Hardware. ID & Compatible. Id based on data from the Device Relationship Metadata <pnpx: Hardware. Id> <pnpx: Compatible. Id>
Steps 7 & 8 – Print Service Pn. P Notification to FD and WSDMon Spooler WSD Port Monitor 8 Function Discovery (FD) 7 Print Service FDO FD gets Pn. P notification of the new WS-Printer Service device object FD adds device to the correct category/subcategory and creates notification which is picked up by WSDMon
Step 9 – Get. Metadata WSDMon activates the WS Print. Proxy via the FD function instance and gets needed information from the device Uses Get. Metadata calls or Print Service methods Gets device 1284 ID and determines port name WSDMon calls UMBus with info needed to create a Print Device Physical Device Object (PDO) in RAW mode This gets Pn. P started installing the Print Object in the spooler (Printers and Faxes folder) WSD Port Monitor Spooler 9 User-Mode Enabled Bus Enumerator (UMBus)
Steps 10 & 11 – PDO Creation and Driver Install Pn. P-Printer Class Installer 11 Print Device PDO 10 User-Mode Enabled Bus Enumerator (UMBus) UMBus creates a Print Device PDO This PDO contains the Hardware ID, Port. Name, Printer. Name, Location and comment field of the associated printer Pn. P searches installed INFs to find an INF that matches If no INF is found the Found New Hardware Wizard (FNHM) starts If an INF is found (or selected in the FNHW) Pn. P invokes the associated class installer, in this case the Printer Class Installer Install continues just like local Pn. P using the supplied information from the Print Device PDO to complete the installation
Printing Operation Step By Step A B D WSD Port Monitor Driver C App E F Spooler G Queue View
Step A & B – Driver Initialization Bi-di enabled Driver queries device for configuration Driver A WSD Port Monitor B Driver uses Bi-di schema to request device configuration WSD Port Monitor uses Get. Printer. Elements operation to retrieve data from printer WSDMon converts XML data to Bi-di Schema responses
Step C – Application prints a document App C WSD Port Monitor Application uses Dev. Caps to get accurate device capabilities Application formats the document based on current device capabilities Application begins rendering the document
Step D & E – WSD Port Monitor prints a document WSDMon sends Create. Print. Job operation to prepare device for print data WSD Port Monitor D Create. Print. Job response E contains device Job. ID On first Write. Port call WSDMon creates Send. Document opreation Device Job. ID and Job data transferred as part of Send. Document operation using MTOM
Step F & G – Job. End. State Event and Rich Status Queue View F WSD Port Monitor G Printer send Job. End. State event when the print job finishes WSD Port Monitor creates Rich Status notification based on information in the event Job Status in Queue View is updated after Set. Job call
Scanning with Web Services for Devices
Scanner Installation Step By Step WIA Service WSD Scan Driver 1 8 Function Discovery (FD) 4 4 Scan Service FDO IPBus. Enumerator 6 6 5 5 User-Mode Enabled Bus Enumerator (UMBus) 3 WS-Discovery Provider 2
Step 1 – WIA Service and Scan Class Driver Initialization WSD Scan Driver WIA Service 1 Function Discovery (FD) WIA Service starts up or User starts a WIA application WIA Service queries Pn. P for all existing Scan devices and creates the appropriate objects (Step 8)
Steps 2 & 3 – Scanner Announcement and Discovery Function Discovery (FD) 3 WS-Discovery Provider 2 Scanner announces presence on the network by a WS-Discovery “Hello” message or responds to a Probe message from user opening Computers & Devices WS-Discovery provider recognizes the device and publishes it to Function Discovery (FD) Device Instance in FD contains all the basic device Metadata Device enabled for install if it contains Pn. P-X related metadata
Steps 4 & 5 – Notification from FD and Devnode Creation Function Discovery (FD) 4 IPBus. Enumerator 5 User-Mode Enabled Bus Enumerator (UMBus) From Within Computers & Devices the User adds/installs discovered device to Association Database IPBus. Enum gets a notification of the newly associated Network Device IPBus. Enum reads data from the new instance and uses the COM interface to the User-Mode Enabled Bus Enumerator (UMBus) to tell UMBus to create a new WS Print Service Dev. Node
Steps 6 – Create Scanner Service Devnode Scan Service FDO 6 User-Mode Enabled Bus Enumerator (UMBus) UMBus creates a File Device Object (FDO) for the WS-based Scanner Service This FDO has a Hardware. ID & Compatible. Id based on data from the Device Relationship Metadata <pnpx: Hardware. Id> <pnpx: Compatible. Id>
Step 7 – Pn. P Notification and WSD Scan Driver Object Initialization WIA Service WSD Scan Driver 7 Scan Service FDO WIA Service gets Pn. P notification of the new WSScanner Service device object WIA creates a unique identifier for the device WSD Scan Driver instance is loaded for the new scanner Scan Service Function Instance is activated and the Scan. Proxy DLL is loaded Scanner installation is complete!
Scanning Operation in the Home - Step By Step A WSD Scan Driver C B D WIA Service
Step A – PC Registers with Scanner WIA Service WSD Scan Driver A At scan object creation the PC creates scan destination(s) in the scan device Assigns device a unique identifier Subscribes for Scan. Available. Event with wscn: Scan. Destinations extension operation to set display name for current PC Receives scan context from device
Steps B & C – User Initiates Scan WIA Service WSD Scan Driver C User selects destination from device display panel User presses scan button Device sends a Scan. Available. Event to selected PC Event contains scanner identifier and scan context B Note: this could also be initiated from an application on the PC if scanner doesn’t have LCD or multi-PC capability
Step D – Client Scans From Device WIA Service WSD Scan Driver D Client uses Create. Scan. Job & Retreive. Image operations to initiate scan and retrieve scan data Scan ticket in Create. Scan. Job operation contains desired scanning parameters Scan data is retrieved as part of the Retrieve. Image operation response in any form using MTOM
XML Messages for Printing
Get. Printer. Elements Request Example <SOAP: Envelope xmlns: SOAP="http: //schemas. xmlsoap. org/soap/envelope/" xmlns: SOAP-ENC="http: //schemas. xmlsoap. org/soap/encoding/" xmlns: xsi="http: //www. w 3. org/2001/XMLSchema-instance" xmlns: xsd="http: //www. w 3. org/2001/XMLSchema" xmlns: wprt="http: //schemas. microsoft. com/windows/2005/05/wdp/print"> <SOAP: Header> <wsa: Action> http: //schemas. microsoft. com/windows/2005/05/wdp/print/Get. Printer. Eleme nts </wsa: Action> --- Header removed for Brevity --</SOAP: Header <SOAP: Body> <wprt: Get. Printer. Elements. Request> <wprt: Requested. Elements> <wprt: Name>wprt: Printer. Configuration</wprt: Name> </wprt: Requested. Elements> </wprt: Get. Printer. Elements. Request > </SOAP: Body> </SOAP: Envelope>
Get. Printer. Elements Response Example <SOAP: Envelope xmlns: SOAP="http: //schemas. xmlsoap. org/soap/envelope/" xmlns: SOAP-ENC="http: //schemas. xmlsoap. org/soap/encoding/" xmlns: xsi="http: //www. w 3. org/2001/XMLSchema-instance" xmlns: xsd="http: //www. w 3. org/2001/XMLSchema" xmlns: wprt="http: //schemas. microsoft. com/windows/2005/05/wdp/pr int"> <SOAP: Header> <wsa: Action> http: //schemas. microsoft. com/windows/2005/05/wdp/print/Get. Print er. Elements. Response </wsa: Action> --- Header removed for Brevity --</SOAP: Header <SOAP: Body> <wprt: Get. Printer. Elements. Response>. . . </wprt: Get. Printer. Elements. Response> </SOAP: Body> </SOAP: Envelope>
Create. Print. Job Request Example <SOAP: Envelope xmlns: SOAP="http: //schemas. xmlsoap. org/soap/envelope/" xmlns: SOAP-ENC="http: //schemas. xmlsoap. org/soap/encoding/" xmlns: xsi="http: //www. w 3. org/2001/XMLSchema-instance" xmlns: xsd="http: //www. w 3. org/2001/XMLSchema" xmlns: wprt="http: //schemas. microsoft. com/windows/2005/05/wdp/print"> <SOAP: Header> <wsa: Action> http: //schemas. microsoft. com/windows/2005/05/wdp/print/Create. Print. Jo b </wsa: Action> --- Header removed for Brevity --</SOAP: Header <SOAP: Body> <wprt: Create. Print. Job. Request>. . . </wprt: Create. Print. Job. Request> </SOAP: Body> </SOAP: Envelope>
Create. Print. Job Response Example <SOAP: Envelope xmlns: SOAP="http: //schemas. xmlsoap. org/soap/envelope/" xmlns: SOAP-ENC="http: //schemas. xmlsoap. org/soap/encoding/" xmlns: xsi="http: //www. w 3. org/2001/XMLSchema-instance" xmlns: xsd="http: //www. w 3. org/2001/XMLSchema" xmlns: wprt="http: //schemas. microsoft. com/windows/2005/05/wdp/pr int"> <SOAP: Header> <wsa: Action> http: //schemas. microsoft. com/windows/2005/05/wdp/print/Create. Pr int. Job. Response </wsa: Action> --- Header removed for Brevity --</SOAP: Header <SOAP: Body> <wprt: Create. Print. Job. Response>. . . </wprt: Create. Print. Job. Response> </SOAP: Body> </SOAP: Envelope>
Send. Document Request Example mime-version: 1. 0 Content-Type: multipart/related; type=application/ xop+xml; boundary=“--=_Next. Part_123_321_0000000. 3 E 9 F 5 D”; start=”<Operation. Request>”; start=”<Operation. Request startinfo=application/soap+xml ----=_Next. Part_123_321_0000000. 3 E 9 F 5 D Content-Type: application/ xop+xml; type=application/ soap_xop+xml charset=UTF-8 xop+xml; charset=UTF-8 Content-Transfer-Encoding: binary Content-ID: <Operation. Request> <Operation. Request <? xml version="1. 0" encoding="utf-8"? > <soap: Envelope xmlns: soap="http: //schemas. xmlsoap. org /soap/envelope/" xmlns: soap="http: //schemas. xmlsoap. org xmlns: wsdp="http: //schemas. xmlsoap. org/ws/2004/08/devprof" xmlns: wsa="http: //schemas. xmlsoap. org/ws/2003/03/addressing" xmlns: wprt="http: //schemas. microsoft. com/windows/2005/05/wdp/print" xmlns: xmlmime=’http: //www. w 3. org/2004/11/xmlmime’ xmlns: xop=’http: //www. w 3. org/2004/08/xop/include’ soap: encoding. Style ='http: //www. w 3. org/2002/12/soap-encoding' > <soap: Header> <wsa: To>uuid: Device. UUID</wsa: To> <wsdp: Service. Id>uri: Idof. This. Service</wsdp: Service. Id> uri: Idof. This. Service </wsdp: Service. Id> <wsa: Action> http: //schemas. microsoft. com/windows/2005/05/wdp/print/Send. Document </wsa: Action> <wsa: Message. ID>uuid: Unique. Msg. Id</wsa: Message. ID> </soap: Header> </
Send. Document Request Example (cont. ) <soap: Body> <wprt: Send. Document. Request> <wprt: Job. Id>Id. From. Create. Job. Request</wprt: Job. Id> <wprt: Document. Description> <wprt: Document. Id>Doc. Id. Number</wprt: Document. Id> <wprt: Compression>None</wprt: Compression> <wprt: Document. Format> application/octetstream</wprt: Document. Format> <wprt: Document. Name>Example. xml</wprt: Document. Name> </wprt: Document. Description> <wprt: Last. Document>true</wprt: Last. Document> <wprt: Document. Data xmlmime: content. Type=”application/postscript”> <xop: Include href=”cid: 000001” /> </wprt: Document. Data> </wprt: Send. Document. Request> </soap: Body> </soap: Envelope> ----=_Next. Part_123_321_0000000. 3 E 9 F 5 D Content-Type: application/postscript; Content-Transfer-Encoding: binary Content-ID: <000001> Document PDL Data
Send. Document Response Example <SOAP: Envelope xmlns: SOAP="http: //schemas. xmlsoap. org/soap/envelope/" xmlns: SOAP-ENC="http: //schemas. xmlsoap. org/soap/encoding/" xmlns: xsi="http: //www. w 3. org/2001/XMLSchema-instance" xmlns: xsd="http: //www. w 3. org/2001/XMLSchema" xmlns: wprt="http: //schemas. microsoft. com/windows/2005/05/wdp/print"> <SOAP: Header> <wsa: Action> http: //schemas. microsoft. com/windows/2005/05/wdp/print/Send. Document. Response </wsa: Action> --- Header removed for Brevity --</SOAP: Header <SOAP: Body> <wprt: Send. Document. Response/> </SOAP: Body> </SOAP: Envelope>
XML Messages for Scanning
Subscribe Request Example <soap: Envelope xmlns: soap="http: //www. w 3. org/2003/05/soap-envelope" xmlns: wsa="http: //schemas. xmlsoap. org/ws/2004/08/addressing" xmlns: wse="http: //schemas. xmlsoap. org/ws/2004/08/eventing" xmlns: wsdp="http: //schemas. xmlsoap. org/ws/2005/05/devprof" xmlns: wscn="http: //schemas. microsoft. com/windows/2005/08/wdp/scan"> <soap: Header> <wsa: Action>http: //schemas. xmlsoap. org/ws/2004/08/eventing/Subscribe</wsa: Action> <wsdp: Service. Id>uri: scn</wsdp: Service. Id> --- Headers removed for Brevity --</soap: Header> <soap: Body> <wse: Subscribe> <wse: Delivery Mode="http: //schemas. xmlsoap. org/ws/2004/08/eventing/Delivery. Modes/Push"> <wse: Notify. To> <wsa: Address> http: //157. 56. 92. 87: 5357/872 b 563 f 2832 -49 eb-8 e 80 -a 721 fe 7 a 7 fd 9 </wsa: Address> </wse: Notify. To> </wse: Delivery> <wse: Expires>PT 10 M</wse: Expires> <wse: Filter Dialect="http: //schemas. xmlsoap. org/ws/2005/05/devprof/Action"> http: //schemas. microsoft. com/windows/2005/08/wdp/scan/Scan. Available. Event </wse: Filter> <wscn: Scan. Destinations> <wscn: Scan. Destination> <wscn: Client. Display. Name>Scan to wscn: Client. Display. Name>Scan MFenelon 2 L</wscn: Client. Display. Name> <wscn: Client. Context>Scan</wscn: Client. Context> </wscn: Scan. Destination> <wscn: Client. Display. Name>Scan for Print to wscn: Client. Display. Name>Scan MFenelon 2 L</wscn: Client. Display. Name> <wscn: Client. Context>Scan. To. Print</wscn: Client. Context> </wscn: Scan. Destinations>
Subscribe (Scan. Available. Event) Response Example <soap: Envelope xmlns: soap="http: //www. w 3. org/2003/05/soap-envelope" xmlns: wsa="http: //schemas. xmlsoap. org/ws/2004/08/addressing" xmlns: wse="http: //schemas. xmlsoap. org/ws/2004/08/eventing" xmlns: wsdp="http: //schemas. xmlsoap. org/ws/2005/05/devprof" xmlns: wscn="http: //schemas. microsoft. com/windows/2005/08/wdp/scan"> <soap: Header> <wsa: Action>http: //schemas. xmlsoap. org/ws/2004/08/eventing/Subscribe. Response</wsa: Action> --- Headers removed for Brevity --- </soap: Header> <soap: Body> <wse: Subscribe. Response> <wse: Subscription. Manager> <wsa: Address>http: //157. 56. 88. 113: 80/Test. Device</wsa: Address> <wsa: Reference. Properties> <wsdp: Service. Id>uri: scn</wsdp: Service. Id> <wse: Identifier>uuid: 0 c 27676 b-e 507 -4837 -951249 d 64640991 d</wse: Identifier> </wsa: Reference. Properties> </wse: Subscription. Manager> <wse: Expires>PT 9 M 59. 9531289 S</wse: Expires> <wscn: Destination. Responses> <wscn: Destination. Response> <wscn: Client. Context>Scan</wscn: Client. Context> <wscn: Destination. Token>113527 a 8 -0908 -4222 -bd 6 cwscn: Destination. Token> 9 c 95 d 302 c 454</wscn: Destination. Token> </wscn: Destination. Response> <wscn: Client. Context>Scan. To. Print</wscn: Client. Context> <wscn: Destination. Token>6 fcbbc 0 f-c 035 -41 ca-a 912 f 6961 a 2 e 2257</wscn: Destination. Token> </wscn: Destination. Response> </wscn: Destination. Responses> </wse: Subscribe. Response> </soap: Body>
Scan. Available. Event Example <soap: Envelope xmlns: soap="http: //www. w 3. org/2003/05/soap-envelope" xmlns: wsa="http: //schemas. xmlsoap. org/ws/2004/08/addressing" xmlns: wscn="http: //schemas. microsoft. com/windows/2005/08/wdp/scan"> <soap: Header> <wsa: To> http: //157. 56. 92. 87: 5357/872 b 563 f-2832 -49 eb-8 e 80 a 721 fe 7 a 7 fd 9 </wsa: To> <wsa: Action> http: //schemas. microsoft. com/windows/2005/08/wdp/scan/Scan. Available. E vent </wsa: Action> </soap: Header> <soap: Body> <wscn: Scan. Available. Event> <wscn: Client. Context>Scan</wscn: Client. Context> <wscn: Scan. Identifier> a 74 dc 73 c-34 b 6 -4 e 99 -a 724 -c 006 f 4625 b 68 </wscn: Scan. Identifier> </wscn: Scan. Available. Event> </soap: Body> </soap: Envelope>
Create. Scan. Job Request Example <soap: Envelope xmlns: soap="http: //www. w 3. org/2003/05/soap-envelope" xmlns: wsa="http: //schemas. xmlsoap. org/ws/2004/08/addressing" xmlns: wsdp="http: //schemas. xmlsoap. org/ws/2005/05/devprof" xmlns: wscn="http: //schemas. microsoft. com/windows/2005/08/wdp/scan"> <soap: Header> <wsa: To>http: //157. 56. 88. 113: 80/Test. Device</wsa: To> <wsa: Action> http: //schemas. microsoft. com/windows/2005/08/wdp/scan/Create. Scan. Job </wsa: Action> <wsdp: Service. Id>uri: scn</wsdp: Service. Id> --- Headers removed for Brevity --</soap: Header> <soap: Body> <wscn: Create. Scan. Job. Request> <wscn: Scan. Identifier> a 74 dc 73 c-34 b 6 -4 e 99 -a 724 c 006 f 4625 b 68</wscn: Scan. Identifier> <wscn: Destination. Token> 113527 a 8 -0908 -4222 -bd 6 c 9 c 95 d 302 c 454</wscn: Destination. Token> <wscn: Scan. Ticket> <wscn: Job. Description> <wscn: Job. Name>Get. Image from Scan. Available. Event</wscn: Job. Name> <wscn: Job. Originating. User. Name> MFenelon</wscn: Job. Originating. User. Name>
Create. Scan. Job Request Example (Cont. ) <wscn: Document. Parameters> <wscn: Format>exif</wscn: Format> <wscn: Images. To. Transfer>1</wscn: Images. To. Transfer> <wscn: Input. Source>Platen</wscn: Input. Source> <wscn: Input. Size> <wscn: Input. Media. Size> <wscn: Width>1000</wscn: Width> <wscn: Height>1000</wscn: Height> </wscn: Input. Media. Size> </wscn: Input. Size> <wscn: Rotation>0</wscn: Rotation> <wscn: Media. Sides> <wscn: Media. Front> <wscn: Color. Processing>RGB 24</wscn: Color. Processing> <wscn: Resolution> <wscn: Width>200</wscn: Width> </wscn: Resolution> </wscn: Media. Front> </wscn: Media. Sides> </wscn: Document. Parameters> </wscn: Scan. Ticket> </wscn: Create. Scan. Job. Request>
Create. Scan. Job Response Example <soap: Envelope xmlns: soap="http: //www. w 3. org/2003/05/soap-envelope" xmlns: wsa="http: //schemas. xmlsoap. org/ws/2004/08/addressing" xmlns: wsdisco="http: //schemas. xmlsoap. org/ws/2005/04/discovery" xmlns: wsdp="http: //schemas. xmlsoap. org/ws/2005/05/devprof" xmlns: wscn="http: //schemas. microsoft. com/windows/2005/08/wdp/scan"> <soap: Header> <wsa: Action> nse http: //schemas. microsoft. com/windows/2005/08/wdp/scan/Create. Scan. Job. Respo </wsa: Action> --- Headers removed for Brevity --</soap: Header> <soap: Body> <wscn: Create. Scan. Job. Response> <wscn: Job. Id>1</wscn: Job. Id> <wscn: Job. Token>b 5838 c 21 -63 a 1 -4 e 99 -a 724 b 459218 cae 7 f</wscn: Job. Token> <wscn: Image. Informaiton>. . </wscn: Image. Information> <wscn: Document. Final. Parameters>. . </wscn: Document. Final. Parameters> </wscn: Create. Scan. Job. Response> </soap: Body> </soap: Envelope>
Retrieve. Image Request Example <soap: Envelope xmlns: soap="http: //www. w 3. org/2003/05/soap-envelope" xmlns: wsa="http: //schemas. xmlsoap. org/ws/2004/08/addressing" xmlns: wsdp="http: //schemas. xmlsoap. org/ws/2005/05/devprof" xmlns: wscn="http: //schemas. microsoft. com/windows/2005/08/wdp/scan"> <soap: Header> <wsa: Action> http: //schemas. microsoft. com/windows/2005/08/wdp/scan/Retrieve. Image </wsa: Action> <wsdp: Service. Id>uri: scn</wsdp: Service. Id> --- Headers removed for Brevity --</soap: Header> <soap: Body> <wscn: Retrieve. Image. Request> <wscn: Job. Id>1</wscn: Job. Id> <wscn: Job. Token>b 5838 c 21 -63 a 1 -4 e 99 -a 724 b 459218 cae 7 f</wscn: Job. Token> <wscn: Document. Description> <wscn: Document. Name>Scanned. Image 001. JPG</wscn: Document. Name> </wscn: Document. Description> </wscn: Retrieve. Image. Request> </soap: Body> </soap: Envelope>
Retrieve. Image Response Example Content-Type: multipart/related; boundary=4 aa 7 d 814 -adc 1 -47 a 2 -8 e 1 c-07585 b 9892 a 4; type="application/xop+xml"; start="<14629 f 74 -2047 -436 c-8046 -5 cac 76 d 280 fc@uuid>"; start-info=application/soap+xml; charset="utf-8” mime-version: 1. 0 --4 aa 7 d 814 -adc 1 -47 a 2 -8 e 1 c-07585 b 9892 a 4 content-type: application/xop+xml; type="application/soap+xml"; charset="utf 8" content-transfer-encoding: binary content-id: <14629 f 74 -2047 -436 c-8046 -5 cac 76 d 280 fc@uuid> <? xml version="1. 0" encoding="utf-8"? > <soap: Envelope xmlns: soap="http: //www. w 3. org/2003/05/soap-envelope" xmlns: wsa="http: //schemas. xmlsoap. org/ws/2004/08/addressing" xmlns: wscn="http: //schemas. microsoft. com/windows/2005/08/wdp/scan"> <soap: Header> <wsa: Action> http: //schemas. microsoft. com/windows/2005/08/wdp/scan/Retrieve. Image. Response </wsa: Action> </soap: Header> <soap: Body> <wscn: Retrieve. Image. Response>
Retrieve. Image Response Example (Cont. ) <wscn: Scan. Data> <XOP: Include xmlns: XOP="http: //www. w 3. org/2004/08/xop/include" href="cid: 1 c 696 bd 7 -005 a-48 d 9 -9 ee 99 adca 11 f 8892@uuid"/> </wscn: Scan. Data> </wscn: Retrieve. Image. Response> </soap: Body> </soap: Envelope> --4 aa 7 d 814 -adc 1 -47 a 2 -8 e 1 c-07585 b 9892 a 4 content-type: application/dib content-transfer-encoding: binary content-id: <1 c 696 bd 7 -005 a-48 d 9 -9 ee 9 -9 adca 11 f 8892@uuid>. . Binary Image data for Scan. . . --4 aa 7 d 814 -adc 1 -47 a 2 -8 e 1 c-07585 b 9892 a 4 --
Скачать презентацию Web Services for Devices Install Printers Scanners
c3d5d15ff13d00b874b011c95a37d22e.ppt