EExecutor
Related Doc:
package exec
do it !
do it !
a list of elements - these will be wrapped in DomAst and added to the tree, so a value should be EVal etc When starting an async action yourself, just return an EEngSuspend and schedule a later DERep to complete this actibity
is this applicable...
is this applicable... applicable?
is this async? note that this flag is just for info, not needed, but do read this comment on async execs
is this async? note that this flag is just for info, not needed, but do read this comment on async execs
If SYNC, we'll wait in this thread on the call to apply - avoid a switch. This is great for local support like DB, logging, echo and other services
If ASYNC, then the engine will actor it out and you'll need to send a DERep to the engine when done so it's more like asking the engine to isolate you rather than promising something
In case this is async, you can return some info/correlation nodes from apply(), which will be added to the tree, after which the engine will NOT mark this node complete. You will send a DERep when done.
Also, while processing, you could add more info nodes to this one and only at the end mark it as done with DERep.
todo will need a DEDetails for the temp info nodes todo implement async, with examples
is this a mock? is it supposed to run in mock mode or not?
is this a mock? is it supposed to run in mock mode or not?
you can have an executor for mock mode and one for normal mode
the list of message specs for this executor - overwrite and return them for content assist
- the name of this executor
a message executor - these can decompose leafs into values or generate more messages
Executors are hardcoded logic, connectors etc