Struct TapHttpServer

pub struct TapHttpServer { /* private fields */ }

TAP HTTP server for handling DIDComm messages.

This server implementation provides endpoints for:

• /didcomm - For processing DIDComm messages via the TAP protocol
• /health - For checking the server’s operational status

The server requires a configuration and a TapNode instance to function. The TapNode is responsible for the actual message processing logic.

Implementations

impl TapHttpServer

pub fn new(config: TapHttpConfig, node: TapNode) -> Self

Creates a new HTTP server with the given configuration and TAP Node.

Parameters

• config - The server configuration including host, port, and endpoint settings
• node - The TAP Node instance used for processing DIDComm messages

Returns

A new TapHttpServer instance that can be started with the start method

pub async fn start(&mut self) -> Result<()>

Starts the HTTP server.

This method:

1. Configures the server routes based on the provided configuration
2. Sets up a graceful shutdown channel
3. Starts the server in a separate Tokio task

The server runs until the stop method is called.

Returns

• Ok(()) - If the server started successfully
• Err(Error) - If there was an error starting the server

pub async fn stop(&mut self) -> Result<()>

Stops the HTTP server.

This method sends a shutdown signal to the server, allowing it to terminate gracefully.

Returns

• Ok(()) - If the server was stopped successfully
• Err(Error) - If there was an error stopping the server

pub fn node(&self) -> &Arc<TapNode>

Returns a reference to the underlying TAP Node.

The TAP Node is responsible for processing DIDComm messages.

pub fn config(&self) -> &TapHttpConfig

Returns a reference to the server configuration.

The server configuration includes settings for the host, port, and endpoint.

pub fn event_bus(&self) -> &Arc<EventBus>

Returns a reference to the event bus.

The event bus is used to publish and subscribe to server events.