Implementing test scenarios for my fledgling usubscription-rust implementation, I've run into meaning-of-life questions regarding the SUBSCRIBED_PENDING und UNSUBSCRIBED_PENDING States.
I get where the idea came from - i.e. have some interactivity/liveliness to show during a remote-topic subscription process.
But: what is the actual value of these states? What would any client really do with the _PENDING information? I mean, a subscribing client cares about whether his (un)subscription request went through ok nor not ok. The _PENDING states really don't do anything to help with that, do they?
Is there a good reason that I'm missing? Or might it be an opportunity to simplify things a bit?
Implementing test scenarios for my fledgling usubscription-rust implementation, I've run into meaning-of-life questions regarding the SUBSCRIBED_PENDING und UNSUBSCRIBED_PENDING States.
I get where the idea came from - i.e. have some interactivity/liveliness to show during a remote-topic subscription process.
But: what is the actual value of these states? What would any client really do with the _PENDING information? I mean, a subscribing client cares about whether his (un)subscription request went through ok nor not ok. The _PENDING states really don't do anything to help with that, do they?
Is there a good reason that I'm missing? Or might it be an opportunity to simplify things a bit?