←back to thread

308 points zdw | 1 comments | | HN request time: 0.498s | source
Show context
ta1243 ◴[] No.44501780[source]
We have a program which the company who developed lost the ability to rebuild the app for some reason.

It has a 500ms timeout to load some settings from a server in the UK via TLS. If it goes more than that 500ms (or something, it's unclear the exact timeout cause) the app just vapourises.

This is fine in the UK, TLS needs about* 3 times RTT to complete though, so an RTT above about 160ms and it's screwed.

Almost all our users are in the UK, europe, mid-east or east coast USA, and in that 160ms RTT range.

We ran into issues when a dozen people tried to use it in Australia, so the principal still happens with some badly written code.

replies(1): >>44507477 #
DmitryOlshansky ◴[] No.44507477[source]
Patching the binary is an option, though it’s tricky I would attempt it anyway.
replies(1): >>44509872 #
1. ta1243 ◴[] No.44509872[source]
Alas an ios app, which is in the app store.

It was a "nice feature" of an older unrelated system, we're going through a procurement to replace it, as patching a binary is fine for me, but not really a supportable solution at an enterprise level :D