mirror of
https://github.com/zeek/zeek.git
synced 2025-10-03 07:08:19 +00:00
f9ac03d6e3
It's easier to track outstanding controller/agent requests via a simple set of pending agent names, and we can remove all of the result aggregation logic since we can simply re-use the results reported by the agents. This can serve as a template for request-response patterns where a client's request triggers a request to all agents, followed by a response to the client once all agents have responded. Once we have a few more of those, it'll become clearer how to abstract this further. |
||
|---|---|---|
| .. | ||
| __load__.zeek | ||
| api.zeek | ||
| boot.zeek | ||
| config.zeek | ||
| log.zeek | ||
| main.zeek | ||
| request.zeek | ||
| types.zeek | ||
| util.zeek | ||