HTTP Messaging Transport

On top of everything else that Wolverine does, the WolverineFx.HTTP Nuget also contains the ability to use HTTP as a messaging transport for Wolverine messaging. Assuming you have that library attached to your AspNetCore project, add this declaration to your WebApplication in your Program.Main() method:

app.MapWolverineHttpTransportEndpoints();

^{snippet source | anchor}

The declaration above is actually using Minimal API rather than native Wolverine.HTTP endpoints, but that's perfectly fine in this case. That declaration also enables you to use Minimal API's Fluent Interface to customize the authorization rules against the HTTP endpoints for Wolverine messaging.

To establish publishing rules in your application to a remote endpoint in another system, use this syntax:

using var host = await Host.CreateDefaultBuilder()
    .UseWolverine(opts =>
    {
        opts.PublishAllMessages()
            .ToHttpEndpoint("https://binary.com/api");
    })
    .StartAsync();

^{snippet source | anchor}

TIP

This functionality if very new, and you may want to reach out through Discord for any questions.