| Re: [ease-dev] Introduction |
Hi, we periodically scan script locations and look for changes in the script content. There we do not parse the code itself, but the keyword section only. This is needed when scripts are used to augment the UI or get triggered on certain actions taken by the user. When the script gets executed we always fetch a fresh copy from its storage location, we do not execute cached data. Caching entire scripts might be another topic. You may make it part of your proposal, however it is not necessary. Instead you should find some way to figure out if it is worth fetching a script again to parse its keywords. Locally we use timestamps to recognize if files have changed. Remotely you might use svn versions, commit hashes or similar means. Christian From: ease-dev-bounces@xxxxxxxxxxx [mailto:ease-dev-bounces@xxxxxxxxxxx] On Behalf Of Utsav Oza Hi Christian, For the scripts stored in workspace and file system locations, the changes made in the scripts are reflected immediately in those scripts, but if we are adding a remote location, after fetching those scripts locally, how will the changes made to those local scripts get reflected on the remote scripts ? Thanks for helping |
Attachment:
smime.p7s
Description: S/MIME cryptographic signature