With the introduction of async fetching (#755), there is a risk that we broke something as Jaybird will not immediately consume the messages returned by the server in response to the fetch. To aid troubleshooting and provide a workaround, we should add a connection property which can be used to disable async fetching.
With the introduction of async fetching (#755), there is a risk that we broke something as Jaybird will not immediately consume the messages returned by the server in response to the fetch. To aid troubleshooting and provide a workaround, we should add a connection property which can be used to disable async fetching.