assistant.net.messaging.generic.server 0.5.182

assistant.net.messaging.generic.server

A messaging server extension which handles messages from a generic client communicating via the same storage.

Configuration

1. Configure message handling on a hosted server

// Startup.cs: void ConfigureServices(IServiceCollection services)
services
    .AddGenericMessageHandling(b => ...) // adds dependencies and initial configuration
    .ConfigureGenericMessageHandling(b => ...); // appends existing configuration (no dependencies are added)

2. Register message handlers

services.ConfigureGenericMessageHandling(b => b.AddHandler<SomeMessageHandler>());
// or named messaging client
services.ConfigureMessageClient(b => b.AddHandler<SomeMessageHandler>());

Note As configured message handler will be run in non-default named options so all its dependencies should be configured the same named context or create own appropriately named DI scope to get dependencies from another named context.

3. Configure a single message handler

services.ConfigureGenericMessageHandling(b => b.UseMongo(o => ...)); // or other provider
// or
services.ConfigureMessageClient(b => b.UseMongo(o => ...)); // or other provider
// or
services.ConfigureStorage(b => b.UseMongo(o => ...)); // or other provider

4. Configure messaging client for generic message handling additionally.

Named configuration

Message handling implementation is based on named options so you can have multiple named message handling servers with different configurations.

services
    .AddGenericMessageHandling(b => b.AddHandler<Handle1>()) // default name registration
    .AddGenericMessageHandling("name-1", b => b.AddHandler<Handle2>()) // named registration
    .AddGenericMessageHandling("name-2", b => b.AddHandler<Handle3>()); // named registration