Mone
that timeout is related to the internal checks the library performs on the existence of the engine (that is the page that connects to the server).
The check is mostly useful in case of an engine shared between two pages (see createEngine with SHARE_SESSION).
In any case the check is usually useless as the library is usually able to detect problems with the engine before the timeout goes off.
The default is 5 seconds and we never had cases where changing it was proven useful.
Note that such setter is going to disappear with the next version of the API.
