Struct TcpStreamServer 

pub struct TcpStreamServer { /* private fields */ }

A TcpStreamServer is a TCP service that listens on a port for incoming response connections. A Response connection is a connection that is established by a client with the intention of sending specific data back to the server.

Implementations

impl TcpStreamServer

pub fn options_builder() -> ServerOptionsBuilder

pub async fn new(options: ServerOptions) -> Result<Arc<Self>, PipelineError>

Trait Implementations

impl ResponseService for TcpStreamServer

fn register<'life0, 'async_trait>( &'life0 self, options: StreamOptions, ) -> Pin<Box<dyn Future<Output = PendingConnections> + Send + 'async_trait>>

where Self: 'async_trait, 'life0: 'async_trait,

Register a new subject and sender with the response subscriber Produces an RAII object that will deregister the subject when dropped

we need to register both data in and data out entries there might be forward pipeline that want to consume the data out stream and there might be a response stream that wants to consume the data in stream on registration, we need to specific if we want data-in, data-out or both this will map to the type of service that is runniing, i.e. Single or Many In // Single or Many Out

todo(ryan) - return a connection object that can be awaited. when successfully connected, can ask for the sender and receiver

OR

we make it into register sender and register receiver, both would return a connection object and when a connection is established, we’d get the respective sender or receiver

the registration probably needs to be done in one-go, so we should use a builder object for requesting a receiver and optional sender