Revision Summary Date Revision History Revision Class Comments 10/22/2006 0.01 Version 0.01 release 1/19/2007 1.0 Version 1.0 release 3/2/2007 1.1 Version 1.1 release 4/3/2007 1.2 Version 1.2 release 5/11/2007 1.3 Version 1.3 release 6/1/2007 1.3.1 Editorial Changed language and formatting in the technical content. 7/3/2007 1.3.2 Editorial Changed language and formatting in the technical content. 7/20/2007 1.3.3 Editorial Changed language and formatting in the technical content. 8/10/2007 1.4 Minor Clarified the meaning of the technical content. 9/28/2007 1.5 Minor Clarified the meaning of the technical content. 10/23/2007 1.6 Minor Clarified the meaning of the technical content.
Method Description The method creates a remote object on a server and returns it to the client. Opnum: 0 The method destroys the specified remote object. Opnum: 1 IRPCRemoteObject_Create (Opnum 0) The IRPCRemoteObject_Create method creates a remote object on a server and returns it to the client. HRESULT IRPCRemoteObject_Create( [in] handle_t hRemoteBinding, [out] PRPCREMOTEOBJECT* ppRemoteObj ); hRemoteBinding: MUST be a client-generated RPC binding handle ( section 2.3) by using a Universal Naming Convention (UNC) name that MUST uniquely identify a print server on the network. ppRemoteObj: MUST be a remote object context handle returned by the server. It MUST be a value. Return Values: This method MUST return zero to indicate success, or an HRESULT value ( section 2.1.1) to indicate failure. The client MUST consider all error return values fatal and report them to the higher-level caller. Exceptions Thrown: No exceptions are thrown beyond those thrown by the underlying RPC protocol . IRPCRemoteObject_Delete (Opnum 1) The IRPCRemoteObject_Delete method destroys the specified remote object. void IRPCRemoteObject_Delete( [in, out] PRPCREMOTEOBJECT* ppRemoteObj ); ppRemoteObj: MUST be the remote object to delete. The handle MUST have been returned by the server in the ppRemoteObj output parameter of a prior call to and MUST NOT have been previously deleted. If this handle were previously registered by a successful call to , then it MUST have been subsequently unregistered by a call to . It MUST NOT be NULL. Upon receipt, the server MUST set the ppRemoteObj value to NULL. Return Values: This method has no return values. Exceptions Thrown: No exceptions are thrown beyond those thrown by the underlying RPC protocol .
A Abstract data model client 69 67 63 73 server 59 44 58 62 15 AsyncUI 19 24 interface 68 59 notification 78 76 XML notification and response formats 24 23 78 76 70 29 72 37 71 35 36 71 31 34 B 77 C 15 87 Client AsyncUI 69 70 68 73 70 68 70 73 69 70 72 71 71 IRPCAsyncNotify 67 68 64 68 68 64 68 68 67 IRPCRemoteObject 63 64 64 64 64 64 64 printer configuration 73 73 74 74 73 74 74 73 73 74 17 D Data model - abstract client 69 67 63 73 server 59 44 58 62 Data types 17 17 19 17 18 E
Enumerations 18 18 Events local client 73 68 64 74 server 61 56 59 63 timer client 73 68 64 74 server 61 56 59 63 Examples AsyncUI notification 78 76 78 76 77 75 F 15 Full IDL 81 82 G 7 I IDL 81 82 80 80 12 Initialization client 70 68 64 73 server 60 45 58 62 Interfaces client 68 64 73 server 59 42 57 62 7 IRPCAsyncNotify interface 64 42 IRPCAsyncNotify_CloseChannel (Opnum 6) method ( 55, 61) 55 49 49 IRPCAsyncNotify_GetNotification (Opnum 5) method ( 53, 61, 63) 53 IRPCAsyncNotify_GetNotificationSendResponse 4) method ( 51, 60) 51 IRPCAsyncNotify_RegisterClient (Opnum 0) method ( 46, 60, 63) 46 48 48 57 58 58 59 59 L Local events client 73 68 64 74 server 61 56 59 63 M Message processing client