Questions about .NET publisher confirms & CreateChannelOptions using RMQ 7.x

[jehrenzweig-captionhealth]

I'm looking for guidance on what CreateChannelOptions to use, when trying to use publisher confirms in the .NET 7.x client.

The .NET "Reliable Publishing with Publisher Confirms" tutorial contains the following statement near the start of the page:

Publisher confirms are enabled at the channel level via the CreateChannelOptions class:

var channelOpts = new CreateChannelOptions(
    publisherConfirmationsEnabled: true,
    publisherConfirmationTrackingEnabled: true,
    outstandingPublisherConfirmationsRateLimiter: new ThrottlingRateLimiter(MAX_OUTSTANDING_CONFIRMS)
);

Because this section appears at the top of the page, I took it to mean that this set of settings should be applied to any/all of the three strategies described further down the page. However, I'm not sure if that's true & I'm hoping the folks here could confirm or refute that assumption.

The info in the "Strategy #3" section appears to use a different set of CreateChannelOptions in the HandlePublishConfirmsAsynchronously() method -- and it overwrites the channelOpts variable used by the other strategies, too:

async Task HandlePublishConfirmsAsynchronously()
{
    Console.WriteLine($"{DateTime.Now} [INFO] publishing {MESSAGE_COUNT:N0} messages and handling confirms asynchronously");

    await using IConnection connection = await CreateConnectionAsync();

    channelOpts = new CreateChannelOptions(publisherConfirmationsEnabled: true, publisherConfirmationTrackingEnabled: false);
    await using IChannel channel = await connection.CreateChannelAsync(channelOpts);

If the CreateChannelOptions settings used in the HandlePublishConfirmsAsynchronously() method to initialize the channel it creates are correct, then at the very least I think a local variable should be used to store those settings, instead of overwriting the global channelOpts variable used by strategies #1 and #2:

async Task HandlePublishConfirmsAsynchronously()
{
    Console.WriteLine($"{DateTime.Now} [INFO] publishing {MESSAGE_COUNT:N0} messages and handling confirms asynchronously");

    await using IConnection connection = await CreateConnectionAsync();

    var asyncHandlerChannelOpts = new CreateChannelOptions(publisherConfirmationsEnabled: true, publisherConfirmationTrackingEnabled: false);
    await using IChannel channel = await connection.CreateChannelAsync(asyncHandlerChannelOpts);

FWIW I'm more than happy to create PRs for any changes that might be needed. However, I wanted to get a better understanding of the correct way to configure RMQ in each of the cases first, since I'm a novice to RabbitMQ as well as the process of migrating the .NET client from 6.x to 7.x.

[lukebakken]

Example #3 is if you want to track publisher confirmations yourself. Unless you have a specific reason for doing so, I would use one of the other methods given in the tutorial.

If you are doing batch publishes, then Example 2 is what you want to do. Experiment with batch sizes and your workload to find the best values.

Thanks again for all your contributions recently!

[jehrenzweig-captionhealth]

So example #3 does have its own set of CreateChannelOptions, which differ from the set used by examples #1 & #2, correct? I just wanna make sure I have it straight in my head.

Thanks again for your help in answering my questions -- happy to do my part!

[lukebakken]

Yep, #3 has its own options.