3 ms·
Agents should use a limited, non-Turing-complete model of evaluation. They could combine API calls locally and run simple FSMs which are easy to formally check
by nine_k 6y ago
Agents should use a limited, non-Turing-complete model of evaluation. They could combine API calls locally and run simple FSMs which are easy to formally check for e.g. absence if loops. This could save round-trips without needing to sacrifice general orthogonal APIs.
Imagine that you could give an app server a formula to combine several API calls, much like you give an SQL server a formula to join and filter tables.
Also, you can easily cache agents by calculating a hash of their source, and call them repeatedly without resending their bodies, much like "prepared statements" work in SQL databases.
- AriaMinaei 6y agoI agree. Though not sure about the non-Turing-complete-ness. How about each agent has a budget. Agents that blow the budget get dropped. Like this: https://gist.github.com/AriaMinaei/69e1a9166e7ffbd61e7f6709d7a819b8 https://gist.github.com/AriaMinaei/69e1a9166e7ffbd61e7f6709d...
- chabad360 6y agoYou sound like your describing (to an extent) GraphQL
- rumanator 6y ago> Agents should use a limited, non-Turing-complete model of evaluation. That doesn't solve any of the caching worries. If it's not a resource then it's not cacheable. > This could save round-trips without needing to sacrifice general orthogonal APIs. Since the inception of HTTP2, a relative large number of requests of cached resources easily beat a relatively small number of requests that are computationally demanding or hit a database.