Subscription message acknowledgement

Product

Hot Chocolate

Is your feature request related to a problem?

Using indirect correlations I can see that some of messages sent to GraphQl subscriptions are not received by the client. I am using HC for three years now to handle tens of thousands of subscriptions. It is handling the task pretty well, but for some reason quite a few messages are lost during delivery to the subscribers. It is not critical issue because it impacts prevailing minority of the client base. However inability to make the message delivery durable causes unpleasant resource utilization in different place.

The solution you'd like

it would be great to have some sort of mode that can be activated for troubleshooting or permanently that uses some sort of hook or handler that accepts an ACK from the client for messages I send to the subscription. I then can correlate messages I sent and receive ACKs for.

No file, test, or entry point is named. Start by tracing Hot Chocolate's GraphQL subscription message-delivery path and define how an optional client acknowledgement hook would expose message identity. Done means the proposed mode can receive acknowledgements that users can correlate with sent subscription messages.