If reads are not repeatable or can't be lost then you really should caching them.
If you can reset your stream, then just start the firehose. Presumably things like a 401 are rare so the waste is minimal.
I could see a use case for this when network IO is prohibitively expensive and needs to be minimized. You're right that there isn't a great solution.
If reads are not repeatable or can't be lost then you really should caching them.
If you can reset your stream, then just start the firehose. Presumably things like a 401 are rare so the waste is minimal.
I could see a use case for this when network IO is prohibitively expensive and needs to be minimized. You're right that there isn't a great solution.