DataMind Oda serves its web interface to a browser on this computer, and the connection behind it runs on a small set of settings: how quickly it retries a dropped connection, how long a browser stays signed in, and how much a single request may carry. This page is the reference for those settings and their defaults. For opening and signing in, see The Oda web app; for the behaviour they produce, see Connection states and recovery.
These settings belong to the connection for your installation of Oda. The values it starts from are:
| Setting | What it decides | Default |
|---|---|---|
| Retry base delay | The first wait before a dropped connection is tried again. | 500 ms |
| Retry growth factor | How much each wait grows from one attempt to the next. | 2; 1 keeps every wait the same |
| Retry cap | The longest wait between attempts. | 10 seconds |
| Slow-service warning | When an attempt that is still getting ready is counted as slow. | 3 seconds |
| Readiness deadline | When an attempt that never becomes ready is cancelled and the next one starts. | 15 seconds |
| Sign-in lifetime | How long a browser keeps its sign-in. | 30 days |
| Request size limit | How much one ordinary request may carry; a streaming request, such as a file upload, is not counted against it. | 300 MiB |
The recovery timings are the ones behind the retry schedule that Connection states and recovery describes. After you change one of them, reload the page: the timings are read when a page loads, so an open page keeps the values it loaded with.
The sign-in is kept as a cookie bound to the exact address that issued it: another address cannot use it, and scripts in the page cannot read it.
Every value is checked before it is used. One that cannot be used is refused instead of being applied: the connection does not load until the value is fixed, and the failure names the value at fault.
Values that are refused include:
When Oda serves the web interface, it puts the connection timings and the address of the service that serves the page into the page itself. The page reads them from there instead of asking for them.
The values are checked before the service starts, so a page never receives one that cannot be used.
The last DataMind server address is remembered and offered as the default the next time a server address is needed, so you do not have to enter it again.
The page keeps using the values it loaded with. Reload it: the recovery timings are read when a page loads, so the new values apply from the next load.
No. A value that would switch recovery off entirely is refused, and there is no setting that stops the retries: while the page is open, Oda keeps trying to bring the connection back on its own.
The connection does not load, and the failure names the value at fault. Fix the value and start again; the list above covers what is refused, from a zero retry base delay to a sign-in lifetime that is out of range.
Yes. The default is 30 days, and your installation can set another lifetime. A value beyond the range the sign-in can keep is refused. The sign-in itself is covered on The Oda web app.
Yes. An ordinary request may carry up to 300 MiB by default, and the limit is sized so that a full batch of images fits in one message, with room to spare. A streaming request, such as a file upload, is not counted against it. Your installation can change the limit; one below what the image limits need is refused. The image limits themselves are on Attach images and files.
Oda puts them into the page when it serves it: the current recovery timings and the address of the service that serves the page. Oda checks the values before the service starts, so a page never receives one that cannot be used.
No. The last DataMind server address is remembered and offered as the default the next time a server address is needed.