autogen/protos
Ryan Sweet 458d273fc4
Refactoring the services and implementing an in-memory runtime for .NET (#4005)
closes #3950 closes #3702

What this is doing:

I am refactoring the services on the .NET runtime and attempting to clarify the naming and organization.
I added this doc to help capture the naming and concepts.
AgentRuntime / Worker should work similar to the python version and enables running the whole agent system in one process. For remote the system uses the versions of the services in the grpc folder.
lots of other bug fixes/threading cleanup - passing cancellation token throughout
Services update clarifies the naming and roles:

Worker: Hosts the Agents and is a client to the Gateway
Gateway:
-- RPC gateway for the other services APIs
-- Provides an RPC bridge between the workers and the Event Bus
Registry: keeps track of the agents in the system and which events they can handle
AgentState: persistent state for agents
2024-11-12 11:04:59 -08:00
..
agent_events.proto Refactoring the services and implementing an in-memory runtime for .NET (#4005) 2024-11-12 11:04:59 -08:00
agent_states.proto refactoring the dotnet folder and namespace structure for better long term maintenance and clarity #3809 (#3810) 2024-10-16 20:09:39 -07:00
agent_worker.proto first draft of stateful persistence grains for each agent.... (#3954) 2024-10-28 17:28:36 -07:00
cloudevent.proto refactoring the dotnet folder and namespace structure for better long term maintenance and clarity #3809 (#3810) 2024-10-16 20:09:39 -07:00