PetterIsberg commented on issue #84:
URL: https://github.com/apache/pulsar-dotpulsar/issues/84#issuecomment-975717538
@blankensteiner We're grateful that you take time to look into this and I'm
sorry for not helping out on this further.
I'm looking through the code now and can see t
PetterIsberg commented on issue #84:
URL: https://github.com/apache/pulsar-dotpulsar/issues/84#issuecomment-931009908
I also think adding pings to the client is a good idea.
I closed my PR as it was meant as an example of how it could be solved. I
should probably have marked it WIP.
--
PetterIsberg commented on issue #84:
URL: https://github.com/apache/pulsar-dotpulsar/issues/84#issuecomment-895873906
I created an example solution of a watchdog as a Pull Request
[https://github.com/apache/pulsar-dotpulsar/pull/85](https://github.com/apache/pulsar-dotpulsar/pull/85).
Pl
PetterIsberg commented on issue #84:
URL: https://github.com/apache/pulsar-dotpulsar/issues/84#issuecomment-895146053
Thank you for the quick answers!
I will try to describe our issue and what we have tested.
We made a test with a small consumer app with state monitoring and client
PetterIsberg commented on issue #84:
URL: https://github.com/apache/pulsar-dotpulsar/issues/84#issuecomment-894640373
We read in the Pulsar documentation that the client has to respond to pings
but is not required to send them.
Is the dotpulsar library sending pings to the server for kee
