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
The current code is a weird set of things that manually decodes and encodes parameters as JSON.
I'm pretty sure that we can have a simple interface where (almost) every call Foo has a FooRequest and FooReply type than are classes that can be jsonified in one step.
There's one or two "funny" calls that are basically unsolicited replies, for example when a new user joins a session.
But I think if we have an orchestrator API that has an interface definition for the outgoing API and an interface definition for the callbacks we're in a situation where it because rather easy to replace the whole orchestrator by something completely different.
The text was updated successfully, but these errors were encountered:
…r records are no longer long-lived in the orchestrator. Does require all participants in the session to have the same definition. Will be fixed with #119.
Followup to #117
The current code is a weird set of things that manually decodes and encodes parameters as JSON.
I'm pretty sure that we can have a simple interface where (almost) every call
Foo
has aFooRequest
andFooReply
type than are classes that can be jsonified in one step.There's one or two "funny" calls that are basically unsolicited replies, for example when a new user joins a session.
But I think if we have an orchestrator API that has an interface definition for the outgoing API and an interface definition for the callbacks we're in a situation where it because rather easy to replace the whole orchestrator by something completely different.
The text was updated successfully, but these errors were encountered: