We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Swarm currently exposes mainly three methods:
Swarm
InitAsync()
RunAsync()
DisposeAsync()
This design has the following problems.
InitContextAsync()
NoSwarmContextException
So I suggest the following interface.
StartAsync()
StopAsync()
The text was updated successfully, but these errors were encountered:
A related issue(#72) was merged.
Sorry, something went wrong.
Merge pull request planetarium#69 from moreal/automate-docker-image-p…
a52120a
…ublish Automate build and push docker image
Merge pull request planetarium#69 from limebell/bugfix/blockrenderer-…
eada8e0
…reorgend RenderReorgEnd to update ReorgEndSubject
Merge pull request planetarium#69 from Atralupus/fix/update-dotnet-ve…
cf075ed
…rsion [Fix] Update dotnet verion to 6.0.x
longfin
No branches or pull requests
Swarm
currently exposes mainly three methods:InitAsync()
: Initializes the internal objects needed for communication and connects to the registered peers.RunAsync()
: Executes event loops to process the message.DisposeAsync()
: Dispose the internal objects and requests the registered peers to delete it.This design has the following problems.
RunAsync()
can be called beforeInitContextAsync()
. but it raisesNoSwarmContextException
.Swarm
in a strange state becauseRunAsync()
does not cancel automatically afterDisposeAsync()
.So I suggest the following interface.
StartAsync()
StopAsync()
The text was updated successfully, but these errors were encountered: