-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
split/rework clients #723
Comments
I think this would create a lot of Additionally, upon onboarding disco I found it very unintuitive that the Some raw ideas to remove/clarify the use of "client":
|
there is currently a mix between a
Client
communicating with the server andClient
s training on a given task.ServerClient
which can list tasks and upon joining one returns a specificDecentralizedClient
orFederatedClient
Task
as this would be the only way to get theses (see split default tasks from core #647)DecentralizedClient
andFederatedClient
would be split in multiple clients{Decentralized,Federated}TrainingClient
which only do the trainingSecureAggregatorClient
for secure aggregation (see aggregator rework #722)onRound*
callbacks indirectionsAggregator
sendLocalWeights(weights: WeightsContainer)
&receiveNetworkWeights*(): AsyncGenerator<WeightsContainer>
The text was updated successfully, but these errors were encountered: