Re: [ease-dev] Introduction

[Christian Pontesegger <christian.pontesegger@xxxxxx>]

Have a look at the existing implementations for Script location parsers. 
We already store timestamps of local files as an indicator when to 
update them. Storing hashes instead will work with minimal effort. The 
whole mechanism of persisting that kind of data is already handled, you 
do not need to care about this.


Christian


On 16.03.2017 15:54, Utsav Oza wrote:
> Hi,
>
> Since we are going to need to compare commit hashes of the cached 
> scripts with the remote scripts, we would require a way to persist and 
> maintain previously fetched commit hashes of the scripts locally. 
> Eclipse does provide means of persisting preferences, application 
> models, widget states etc.but I am not sure about how to persist 
> external data (i.e metadata we obtain for the scripts). What ways can 
> we consider for this purpose ?