| Author | SHA1 | Message | Date |
|---|---|---|---|
|
|
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 |
1 year ago |
|
|
7d1857dae6
|
Clean up the Hello sample, support Aspire 9.0, & fix shutdown in the sample (#4037)
* Wait for acknowledgment when sending message to gRPC channel * Add CancellationToken parameters to API surface * Clean up the Hello sample, support Aspire 9.0, & fix shutdown |
1 year ago |
|
|
14846a3e84
|
first draft of stateful persistence grains for each agent.... (#3954)
* adds Orleans persistence for AgentState |
1 year ago |