3 Protocol Details
The client side of this protocol is simply a pass-through. That is, no additional timers or other state is required on the client side of this protocol. Calls made by the higher-layer protocol or application are passed directly to the transport, and the results returned by the transport are passed directly back to the higher-layer protocol or application.
The client MUST call the NSPINspiBind method, as specified in section 184.108.40.206.1, in order to obtain an RPC context handle to be used in all other NSPI methods. The NSPI NspiUnbind method, as specified in section 220.127.116.11.2, destroys this context handle. Therefore, it is not possible to call any methods other than NspiBind immediately after a call to NspiUnbind. The final method a client MUST call is NspiUnbind.