3.2.4.1 FrsTransport Methods
Methods in RPC Opnum Order
|
Method |
Description |
|---|---|
|
Called by a client to check whether the server is reachable and has been configured to replicate with the client. Opnum: 0 |
|
|
Establishes a logical connection from a client to a server. Opnum: 1 |
|
|
Establishes a logical relationship on the server for a replicated folder. Opnum: 2 |
|
|
Obtains file metadata in the form of updates from a server. Opnum: 3 |
|
|
Obtains the version chain vector persisted on a server. Opnum: 4 |
|
|
Registers an asynchronous callback for a server to provide version chain vectors. Opnum: 5 |
|
|
Retrieves UIDs and GVSNs that a server persists. Opnum: 6 |
|
|
Used by a client to indicate to a server that it could not process an update. Opnum: 7 |
|
|
Transfers successive segments from a file. Opnum: 8 |
|
|
Obtains RDC signature data from a server. Opnum: 9 |
|
|
Registers requests for file ranges on a server. Opnum: 10 |
|
|
Obtains file ranges whose requests have previously been registered on a server. Opnum: 11 |
|
|
Informs the server that the server context information can be released. Opnum: 12 |
|
|
Used by a client to start a file download. Opnum: 13 |
|
|
Opnum14NotUsedOnWire |
Reserved for local use. Opnum: 14 |
|
Used instead of calling RawGetFileData multiple times to obtain file data. This method is not applicable for protocol version 0x00050000. Opnum: 15 |
|
|
Used instead of calling RdcGetFileData multiple times to obtain file data. This method is not applicable for protocol version 0x00050000. Opnum: 16 |
|
|
Informs the server to keep the context information alive. This method is not applicable for protocol versions 0x00050000 and 0x00050002. Opnum: 17 |
In the previous table, the term "Reserved for local use" means that the client MUST NOT send the opnum, and the server behavior is undefined as it does not affect interoperability. <21>