More detailed documentation about nats.c HOT 4 CLOSED

An explanation of robust error handling to handle all possible network failures and race conditions would be immensely useful too, I think.

from nats.c.

@Kazmirchuk I added a FAQ section in the README, hope this helps a bit with some of your questions.

Specifically regarding some of your questions here:

If you have natsOptions_UseOldRequestStyle, what is the new request style then?

There is no API to trigger the new style, it is now the default. The new style improves performance by reducing the number of subscriptions created when doing requests/replies. A single inbox subscription is created per connection and replies are then matched to the appropriate request.

What does this comment means in one of your examples?
// For maximum performance, set no limit on the number of pending messages.
s = natsSubscription_SetPendingLimits(sub, -1, -1);
How do the limits affect performance?

When the publisher publishes as fast as it can, the subscription may fall behind since it is always slower to process a subscribed message than send a message. In order for the example/benchmark to not lose messages and ensure that the subscription will process all sent messages, I set the subscription's queue limits to "unlimited".

In Msgs: 30 - In Bytes: 150 - Delivered: -3689348814741910324 - Pending: 0 - Dropped: 0 - Reconnected: 0
I think, the number of delivered messages got wrong somehow?

I can reproduce this on Windows, I will have a look and create separate issue. Thanks!

from nats.c.

Wow that was quick! Good to know that the negative counter was not a bug in cnats itself.
Thank you so much for the FAQ. It hasn't appeared yet at the main page https://github.com/nats-io/cnats (I guess it needs some time), but I can already read it in the git commit - it is very useful and much more than I could ever expect. Kudos!

from nats.c.

@Kazmirchuk Thanks! I was waiting to get some feedback from you, which apparently is pretty good ;-). I have merged the PR so the FAQ section should now be present in the repo's README at this location.

from nats.c.