Document minimum/maximum allowed `timeout` value about skyring HOT 3 CLOSED

The docs do say that setTimeout is used.
What was unexpected exactly?

from skyring.

Not to nitpick, but the docs imply usage of setTimeout (emphasis mine):

A distributed reliable timer service providing similar functionality to using setTimeout.

The "unexpected" part comes from setting timeouts larger than the maximum allowed by setTimeout, which means the callback is invoked immediately. In my case, this caused certain workflow state in my application to be considered "timed out" far in advance of what was anticipated when I assumed a large default value for a timeout. I've since lowered this default to something within the maximum possible, but it took me a while to discover the reason for why the callback was invoked immediately.

from skyring.

fair enough. if you want to make a PR to update the validator to validate the upper bound - that works for me.

from skyring.