Asset caching and lazy loading about goflow HOT 4 CLOSED

So another approach would be the JSONSchema approach of using $ref as a marker that the resource should be loaded from a URL:

"assets": [
{ "$ref": "https://rpd.io/as/flows/7123..." },
{ "type": "flow", "uuid": "7114...", "name": "..."},
]

Not sure this is better, just different..

from goflow.

Downside of this is you don't know UUID or type or anything ahead of time.

from goflow.

Something else to consider - maybe runs (and contacts?) can be assets sometimes. For example in the trigger flow action case - the caller will need to start a flow with a parent run which belongs to a different contact. It may make sense to model this as an asset because:

• It's immutable for the new flow session
• The engine shouldn't be sending it back in the session and the caller shouldn't be trying to sync it.

The way it might works is:

1. The trigger flow action will return a trigger_flow (?) event which contains the UUID of the parent run.
2. Caller will grab the output of that run (either immediately from the session output or RapidPro could do it later by loading FlowRun.output)
3. Caller starts a new flow session with:
   • That parent as an asset
   • A start_flow event which specifies the parent by UUID

from goflow.

Ya, I think that sounds right to me, that if a run is not part of a session then it is an asset. So I guess it is that runs belong to the session where they were started, otherwise are assets.

from goflow.