[MS-DFSRH]: DFS Replication Helper Protocol Specification

3.2 Client Role Details3.2.1 Abstract Data ModelNo abstract data model is required.3.2.2 TimersNo timers are required.3.2.3 InitializationA client MUST initialize by creating an RPC binding handle to one of the interfaces. For moreinformation and a description of how to get a client-side RPC binding handle for an interface, see[MS-DCOM].No additional initialization is required. The client can call the method of the interfaces immediatelyafter binding.3.2.4 Higher-Layer Triggered EventsAll method invocations are triggered by higher-layer events, such as commands issued inadministrative and diagnostic applications.3.2.5 Message Processing Events and Sequencing RulesThe DFS-R Helper Protocol client does not maintain any state. It MUST send to the server thecommand that is issued by administrative and diagnostic applications. All error codes are returneddirectly to the application.3.2.5.1 Methods with PrerequisitesThe methods of the IServerHealthReport, IADProxy, and IADProxy2 interfaces require noprerequisite calls against the server.3.2.6 Timer EventsNo timer events are used in the DFS-R Helper Protocol.3.2.7 Other Local EventsNo other local events are used in the DFS-R Helper Protocol.[MS-DFSRH] – v20080207DFS Replication Helper Protocol SpecificationCopyright © 2008 Microsoft Corporation.Release: Thursday, February 7, 200867 / 81