Mention IsolateNameServer on isolates.md #6338
Open
+9
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I had a use case where I needed to communicate between isolates. The isolate that needs to send a message was not being created by me but created by a library(flutter_local_notification's notification action)
During my search for a solution to create a communication channel in such a case, I found the excerpt that is just above my addition very confusing since it makes me believe that there is no solution to my problem. (Since I cannot interfere with the
Isolate.spawn
call directly, I thought I cannot obtain a communication channel between the isolates.)This is why I'm doing that contribution to the doc. In my opinion, it is essential to mention the IsolateNameServer class inside isolates.md file, and state that it can allow dynamical registration of ports even though you cannot control the creation of the isolate.
I am very open for any suggestions and other changes to make that mention more blended to the rest of the document.
Thank you in advance!
Contribution guidelines:
dart format
.<?code-excerpt
need to be updated in their source.dart
file as well.