<![CDATA[[resolved] jsReport script: data caching]]>v: 2.1.0

This might be a bit of a noob question: can the data be cached? Is the worker (process) in which you are triggering the script if being terminated after the end or is it persisted? Can I store some values for the future executions?

Consider my scenario, where I have to pull the data from cloud and I need a token. This token has an expiry and I'd like to keep it cached until it expires. How would I do something like that?

Thanks again.

]]>https://forum.jsreport.net/topic/674/resolved-jsreport-script-data-cachingRSS for NodeFri, 15 May 2026 05:27:17 GMTMon, 20 Aug 2018 03:25:06 GMT60<![CDATA[Reply to [resolved] jsReport script: data caching on Mon, 20 Aug 2018 22:47:37 GMT]]>v: 2.1.0

This might be a bit of a noob question: can the data be cached? Is the worker (process) in which you are triggering the script if being terminated after the end or is it persisted? Can I store some values for the future executions?

Consider my scenario, where I have to pull the data from cloud and I need a token. This token has an expiry and I'd like to keep it cached until it expires. How would I do something like that?

Thanks again.

]]>https://forum.jsreport.net/post/3342https://forum.jsreport.net/post/3342Mon, 20 Aug 2018 22:47:37 GMT<![CDATA[Reply to [resolved] jsReport script: data caching on Invalid Date]]>The script runs in the extra process and in extra sandbox. Everything is terminated after it finishes. At least by default.

How about you would save the token to a file and read it from it? Use the file as a cache.

]]>https://forum.jsreport.net/post/3343https://forum.jsreport.net/post/3343Invalid Date<![CDATA[Reply to [resolved] jsReport script: data caching on Invalid Date]]>Hi Jan, not entirely a bad idea... it was not just about the token but could work for larger data too. Thanks

]]>https://forum.jsreport.net/post/3354https://forum.jsreport.net/post/3354Invalid Date