#### [Abblix\.SharedSignals](https://www.abblix.com/en/docs/api/abblix-sharedsignals 'index')
### [Abblix\.SharedSignals\.Receiver\.SecurityEvent](https://www.abblix.com/en/docs/api/abblix-sharedsignals/Abblix.SharedSignals.Receiver.SecurityEvent 'Abblix\.SharedSignals\.Receiver\.SecurityEvent')

## StreamManagementTransport Class

The HTTP transport a receiver manages its streams over: the Event Stream Management API of one
transmitter \(SSF 1\.0 Section 8\.1\)\.

```csharp
public static class StreamManagementTransport
```

Inheritance [System\.Object](https://learn.microsoft.com/en-us/dotnet/api/system.object 'System\.Object') → StreamManagementTransport
### Fields

## StreamManagementTransport\.HttpClientName Field {#Abblix.SharedSignals.Receiver.SecurityEvent.StreamManagementTransport.HttpClientName}

The name the transport's client is registered under, published so a host can configure it
without copying the string:
`services.AddHttpClient(StreamManagementTransport.HttpClientName)` reaches the same
client stream calls are spoken over\.

```csharp
public const string HttpClientName = "StreamManagementClient";
```

#### Field Value
[System\.String](https://learn.microsoft.com/en-us/dotnet/api/system.string 'System\.String')

### Remarks
A NAMED client rather than a typed one, because the client this feeds is not built by the
factory: [StreamManagementClient](https://www.abblix.com/en/docs/api/abblix-sharedsignals/Abblix.SharedSignals.Receiver.SecurityEvent.StreamManagementClient 'Abblix\.SharedSignals\.Receiver\.SecurityEvent\.StreamManagementClient') also takes the transmitter's configuration,
which is data a receiver learns at run time\. [StreamManagementClientFactory](https://www.abblix.com/en/docs/api/abblix-sharedsignals/Abblix.SharedSignals.Receiver.SecurityEvent.StreamManagementClientFactory 'Abblix\.SharedSignals\.Receiver\.SecurityEvent\.StreamManagementClientFactory')
pairs the two, and the name exists so a host still reaches the transport the way it reaches
every other\.