On 24/11/2014 20:28, Jeff Lawson wrote:
It's probably best to perform such long processing as a separate
crontab or daemon that runs your Tcl code, rather than doing it all as
a single Rivet page. Your Rivet page should instead initiate the
processing by using a database or a file to store new "jobs" to be
performed by the backend crontab/daemon, and then return. You can make
a different Rivet page that checks for the results of the processing
that had been stored in a file or in a database updated by your
processing script.
Dear Jeff,
I know about this alternative, but it is not an option to apply it, the
decision has been taken in the past and cannot be changed.
Regards,
George
---------------------------------------------------------------------
To unsubscribe, e-mail: rivet-dev-unsubscr...@tcl.apache.org
For additional commands, e-mail: rivet-dev-h...@tcl.apache.org
