Re-exports§
pub use user::*;
Modules§
Structs§
- Daemon
- The CFDP Daemon is responsible for connecting PDUTransport implementation with each individual SendTransaction and RecvTransaction. When a PDUTransport implementation sends a PDU through a channel, the Daemon distributes the PDU to the necessary Transaction. PDUs are sent from each Transaction directly to their respective PDUTransport implementations.
- Entity
Config - Configuration parameters for transactions which may change based on the receiving entity.
- File
Segment Indication - Indication of the amount of data received from a FileDataPDU
- Finished
Indication - Indication sent when a transaction has finished.
- Metadata
Recv Indication - Indication sent from a Transaction when Metadata has been received
- PutRequest
- Necessary Configuration for a Put.Request operation
- Report
- Simple Status Report Transaction status report
Enums§
- Command
- Lightweight commands the Daemon send to each Transaction
- Indication
- Indications how the Daemon and Transactions relay information back to the User application. Indications are issued at necessary points in each Transaction’s lifetime.
- NakProcedure
- The way the Nak procedure is implemented is the following:
- User
Primitive - Possible User Primitives sent from a end user application via the user primitive channel