Martin Regen b88e2da4d8 Use the request queue to return GoodSubscriptionTransferred immediately (#2280) ...

Issues:
- The expectation is for a client session to receive a `GoodSubscriptionTransferred` status after a subscription is transferred to another session. However there is a corner case exposed in our tests, when all subscriptions are transferred so that the client subscriptiona has no active subscriptions left, only `BadNoSubscription` is returned by the server for allpending requests, instead of the status. As a workaround, to get the status, the client session has to send an additional publish request which is unexpected after a `BadNoSubscription` error.
- The status message is only returned on the next publish request, which can lead to undesired delay of the notification.

Fix: Return the status message immediately if pending requests are available.

Other fixes:
- Make client subscription class cloneable
- Improve the test which didn't receive the status messages
- Use the publish request queue to return a status message immediately

2023-08-25 11:29:16 +02:00

..

AsyncPublishOperation.cs

Update Copyright year to 2020

2020-10-07 18:04:34 +03:00

IMonitoredItem.cs

Improve ResendData server support (#1854)

2022-06-29 06:41:59 +02:00

MonitoredItem.cs

Close socket if a client stops processing responses. (#2110)

2023-04-10 20:49:02 +02:00

PublishingState.cs

Update Copyright year to 2020

2020-10-07 18:04:34 +03:00

SessionPublishQueue.cs

Use the request queue to return GoodSubscriptionTransferred immediately (#2280)

2023-08-25 11:29:16 +02:00

Subscription.cs

Improve ResendData server support (#1854)

2022-06-29 06:41:59 +02:00

SubscriptionManager.cs

Use the request queue to return GoodSubscriptionTransferred immediately (#2280)

2023-08-25 11:29:16 +02:00