Closed GoutsmitSam closed 1 month ago
Great that we have this, but wondering if this is really an 'enhancement' and not an issue/bug.
This is currently under investigation, as it will become necessary short term to upgrade the Pub/Sub to .NET Standard. Reasons:
First step:
The Pub/Sub connector has some issues
However, the packages cannot easily be upgraded. Reason: the pubsub library was never meant to be used via an API. If a listener reads a message from SB it caches it on that instance, if via an API call you try to complete a message and it is not on the same instance as the listener it fails (it's in-memory stateful).
Best to rework them.