You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 27, 2024. It is now read-only.
Issue to track the design of a WASM Agent interacting with a server agent through Router.
Agent registration pre-process:
Router creates a random WS endpoint and supplies this info to the agent. eg ws://agent-server.com/uuid/mailbox
Agent knows the routers endpoint(ws)/DID/Invitation.
Agent connects to the router WS endpoint and does DIDExchange. Puts it's endpoint as something derived from ws://agent-server.com/uuid/<>
The outcome is that the agent DID has claimed a UUID on the router. Any interaction for that UUILD have to be authenticated by the agent DID. Now we can do all the route registration steps and agent can use that endpoint (http) to communicate with other agents.
The text was updated successfully, but these errors were encountered:
Base structure for Route Coordination protocol is added as part of #934. Enhancement and each feature implementation will be added as part of separate Issues.
Issue to track the design of a WASM Agent interacting with a server agent through Router.
Agent registration pre-process:
The outcome is that the agent DID has claimed a UUID on the router. Any interaction for that UUILD have to be authenticated by the agent DID. Now we can do all the route registration steps and agent can use that endpoint (http) to communicate with other agents.
The text was updated successfully, but these errors were encountered: