↧
Both of those are request time-outs, correct? i am concerned with inactivity timeouts not from a request, but where the session identity is lost after no requests from the browser for x time.
- on the client : FoxInCloud.js overridden by xxx.js
<span style="{font-size: xx-small; color: red;}">Code parsing for language: "javascript'" is not currently supported.<br></span> requestTimeoutDev: 600, // {en} DEVELOPMENT : request timeout delay in seconds // {en} when delay times out, an alert appears in HTML page and request is lost // {en} a faily long delay is recommended to let you enough time to debug any possible error // {fr} DÉVELOPPEMENT : délai en secondes avant que la requête n'expire // {fr} quand le délai expire, un message apparaît dans la page HTML et la requête est perdue // {fr} un délai assez long est recommandé pour vous laisser le temps de déboguer le cas échéant requestTimeoutProd: 25, // {en} PRODUCTION: request timeout delay in seconds // {en} when delay times out, an alert appears in HTML page and request is lost // {en} set a delay at least as long as the 'Timeout' value in your wc.ini file // {fr} PRODUCTION : délai en secondes avant que la requête n'expire // {fr} quand le délai expire, un message apparaît dans la page HTML et la requête est perdue // {fr} réglez un délai au moins aussi long que la valeur de 'Timeout' dans votre fichier wc.ini
- on the server through wc.ini!Timeout=60, like any wConnect application
For long requests you can either run several server instances or run an asynchronous process (wwAsyncWebRequest.prg!wwAsyncWebRequest)
HTH,
I am about to investigate a report from a user, but before if anyone knows a simple answer to this: does FiC enforce any kind of inactivity timeout? (Not a server request timeout)
-- thn (FoxInCloud)