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
..
01 - Programming Model.md	Update references (#657)	2024-09-28 04:01:08 +00:00
02 - Topics.md	Initial design proposal for message routing (#245)	2024-08-23 13:31:26 -04:00
03 - Agent Worker Protocol.md	Refactoring the services and implementing an in-memory runtime for .NET (#4005)	2024-11-12 11:04:59 -08:00
04 - Agent and Topic ID Specs.md	Standardize Agent and Topic ID strings + documentation (#638)	2024-09-26 19:45:38 +00:00
05 - Services.md	Refactoring the services and implementing an in-memory runtime for .NET (#4005)	2024-11-12 11:04:59 -08:00