ditto icon indicating copy to clipboard operation
ditto copied to clipboard

HTTP retry mechanism

Open BobClaerhout opened this issue 3 years ago • 2 comments

We have an HTTP-push connection configured to provide digital twin updates to 3rd party webservices. This connection sometimes fails (because of network connectivity, server update on the other end, ...). It would be nice if some retry mechanism would retry the push and not fail immediately. As discussed with @thjaeckle, it's possible to do this using acknowledgements and design a retry mechanism in the business application but in our case the business application is unaware of which connections exist. Therefor it would be nice if the pushing mechanism within ditto is a bit more robust. The proposal is to have specificConfig entries (in this case for HTTP, but might be expanded to other protocols) configuring the retry mechanism on a single connection. This is just the start of the discussion and the details are still to be figured out.

BobClaerhout avatar Dec 22 '22 11:12 BobClaerhout

I think this is a valuable feature to have. One thing to think about is to ensure that (possible massive retries) do not impede the rest of Ditto. I. e. we should establish boundaries which might not be harmed by user config.

jufickel-b avatar Dec 23 '22 08:12 jufickel-b

@thjaeckle should I pick this up for contribution ?

Abhijeetmishr avatar Mar 06 '23 13:03 Abhijeetmishr