an applicable or message executor - can execute a message
these are assignable and take action when assigned
basic connectors - these maintain state and have a lifecycle, possibly actors etc
format template results: if the current message has a template for a "result" then apply it.
execute tests
a message executor - these can decompose leafs into values or generate more messages
a message executor - these can decompose leafs into values or generate more messages
Executors are hardcoded logic, connectors etc
a single snakk call to make - goes beyond Snakk.body
a single snakk call to make - goes beyond Snakk.body
http, telnet
GET, POST, open etc
manage all connectors
manage all executors
per-realm statics
per-realm statics
todo right now I accept and grow with any realm - when doing realm-node assignments, clean that up
picked up and executed elsewhere - works with the SnakkCallServer
format template results: if the current message has a template for a "result" then apply it.
If a message has a "payload" type template, this is it's executor.
this is just a simple use of templates - equivalent to setting payload to a templatized value
todo simpler mechanism, something like: (payload = """tempalte ${ss}""" as Json) but that would not be recognized as a template by tspecs