API Communications - Best Practices
Dialing... busy... retrying... dialing... Remember the days of dial-up internet? The ever-so-common scenario where you heard a busy signal. As frustrating as this was, the great part was your mode...
Forum Discussion
Dan - thanks for engaging. It is true that this is mostly geared towards server-side operations. Code running client-side, to your point, probably has less likelihood of breaking down than a complex web of servers, network layers, etc. Whenever we post content like this, we want to make sure we draw the line between sharing best practices and being overly technical.
In your example of JavaScript, one of the differences is loading JavaScript that co-loads with the QB UI vs having a custom JavaScript interface that sits "on top of" Quick Base. Many customers have their own user interface. In these scenarios, transient faults could occur transparently to the user since they aren't looking at Quick Base.
In your example of JavaScript, one of the differences is loading JavaScript that co-loads with the QB UI vs having a custom JavaScript interface that sits "on top of" Quick Base. Many customers have their own user interface. In these scenarios, transient faults could occur transparently to the user since they aren't looking at Quick Base.