Skip to main content

CommandsSender

ocpi_kit::server

Trait CommandsSender 

Source 
pub trait CommandsSender:
    Send
    + Sync
    + 'static {
    // Required method
    fn command_result(
        &self,
        unique_id: String,
        result: CommandResult,
        context: RequestContext,
    ) -> impl Future<Output = Handled<()>> + Send;
}
Available on crate feature server only.
Expand description

The eMSP side of the Commands module: receiving the asynchronous result.

Spec: 2.3.0 §mod_commands_commands_module

Required Methods§

Source

fn command_result( &self, unique_id: String, result: CommandResult, context: RequestContext, ) -> impl Future<Output = Handled<()>> + Send

POST {response_url} — the Charge Point’s eventual answer.

The unique_id is whatever the implementation put in the response_url when it sent the command, which is how the result is matched to the request:

This URL might contain a unique ID to be able to distinguish between StartSession requests.

Dyn Compatibility§

This trait is not dyn compatible.

In older versions of Rust, dyn compatibility was called "object safety".

Implementors§