If an extension is called that uses builtins like gohan_sync_watch, the time spent in the builtin is included in the total time spent in the extension. Since, the default time limit for an extension execution is 30 secs, it effectively disallows long-polling from extensions with an arbitrary timeout. In large scale solutions, 30 secs long-polling is not enough.
A proposed change is to add a configuration option 'builtin-timelimit' and to not include time spent in a builtin to the total execution time of the executing extension. A time spent in a builtin should counted separately and be limited according to the configuration setting mentioned above.
If an extension is called that uses builtins like gohan_sync_watch, the time spent in the builtin is included in the total time spent in the extension. Since, the default time limit for an extension execution is 30 secs, it effectively disallows long-polling from extensions with an arbitrary timeout. In large scale solutions, 30 secs long-polling is not enough.
A proposed change is to add a configuration option 'builtin-timelimit' and to not include time spent in a builtin to the total execution time of the executing extension. A time spent in a builtin should counted separately and be limited according to the configuration setting mentioned above.