Skip to content

Fixed link for distributed-process-async #43

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.

Sign up for GitHub

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

Merged
hyperthunk merged 1 commit into from
Feb 23, 2018
Merged

Fixed link for distributed-process-async #43

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion tutorials/4ch.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -351,7 +351,7 @@ submitter with the handle, so we end up with one field for the active (running)
tasks and another for the queue of accepted (but inactive) ones, as expected.

Since we cannot wait on all these `Async` handles at once whilst we're supposed to
be accepting new messages from clients - actually, /async/ does provide an API for
be accepting new messages from clients - actually, [distributed-process-async][6] does provide an API for
multiplexing on async results, but that's no use here - instead we will monitor the
async tasks and pull the results when we receive their monitor signals. So for the
active tasks, we'll need to store a `MonitorRef` and a reference to the original
Expand Down Expand Up @@ -668,3 +668,4 @@ additional book keeping data.
[3]: https://github.com/haskell-distributed/distributed-process-task
[4]: https://github.com/haskell-distributed/distributed-process-extras/blob/master/src/Control/Distributed/Process/Extras/UnsafePrimitives.hs
[5]: /documentation.html
[6]: https://hackage.haskell.org/package/distributed-process-async