Come up with URL fingerprint strategy

nyaruka / goflow

Flow engine for RapidPro/TextIt.

Other

45 stars 20 forks source link

Come up with URL fingerprint strategy #106

Closed nicpottier closed 6 years ago

nicpottier commented 7 years ago

For URLs RapidPro generates for dependencies, need to decide how we make these unique / change when things change. (such as a contact field being added or group deleted etc..)

rowanseymour commented 6 years ago

We currently generate a new fingerprint each time on the rapidpro side so effectively nothing is cached between requests to the flowserver. Obviously need to optimize this once we move beyond just testing simulator runs.

rowanseymour commented 6 years ago

We now have type specific fingerprints based on the latest modified on date for each type