Trait TaskBroker 

pub trait TaskBroker: Send + Sync {
    // Required methods
    fn submit(
        &self,
        task: AgentTask,
    ) -> impl Future<Output = Result<String>> + Send;
    fn status(
        &self,
        task_id: &str,
    ) -> impl Future<Output = Result<TaskStatus>> + Send;
    fn receive(&self) -> impl Future<Output = Result<Option<AgentTask>>> + Send;
    fn complete(
        &self,
        task_id: &str,
        result: TaskResult,
    ) -> impl Future<Output = Result<()>> + Send;
    fn fail(
        &self,
        task_id: &str,
        error: String,
    ) -> impl Future<Output = Result<()>> + Send;

    // Provided method
    fn none_means_closed(&self) -> bool { ... }
}

Trait for distributing agent tasks across workers.

Implement this for your message broker (AWS SQS, Google Pub/Sub, Azure Service Bus, Redis, NATS, RabbitMQ, etc.) to enable multi-process agent execution.

Required Methods

fn submit(&self, task: AgentTask) -> impl Future<Output = Result<String>> + Send

Submits a task for execution. Returns the task ID.

fn status( &self, task_id: &str, ) -> impl Future<Output = Result<TaskStatus>> + Send

Queries the current status of a task.

fn receive(&self) -> impl Future<Output = Result<Option<AgentTask>>> + Send

Waits for a task and returns it.

Returns Ok(None) when no task was obtained. What that means depends on none_means_closed:

• none_means_closed() == true — the broker is permanently closed and no further tasks will ever arrive; callers should stop polling.
• none_means_closed() == false (the default) — the queue was merely idle for one poll interval (e.g. a blocking-pop timeout or an empty fetch); callers should keep polling.

fn complete( &self, task_id: &str, result: TaskResult, ) -> impl Future<Output = Result<()>> + Send

Marks a task as completed with the given result.

fn fail( &self, task_id: &str, error: String, ) -> impl Future<Output = Result<()>> + Send

Marks a task as failed with an error message.

Provided Methods

fn none_means_closed(&self) -> bool

Whether receive returning Ok(None) means the broker is permanently closed rather than momentarily idle.

Network brokers (Redis, NATS, SQS, Pub/Sub, Service Bus, …) poll with a timeout and legitimately come up empty when the queue is idle, so the default is false: an empty receive is a transient condition and the caller should retry. Brokers with a real end-of-stream signal (e.g. an in-process channel whose senders are gone, or a cancelled AMQP consumer) override this to true so workers can shut down promptly.

Dyn Compatibility

This trait is not dyn compatible.

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

Implementors