Created
December 6, 2011 00:25
-
-
Save 7sharp9/1436079 to your computer and use it in GitHub Desktop.
new pipelets loop
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
let computeAndRoute data routes = async{data |> transform |> router <| routes} | |
let mailbox = MailboxProcessor.Start(fun inbox -> | |
let rec loop routes = async { | |
let! msg = inbox.Receive() | |
match msg with | |
| Payload(data) -> | |
ss.Release() |> ignore | |
Async.StartWithContinuations(computeAndRoute data routes, ignore, errors, ignore) | |
return! loop routes | |
| Attach(stage) -> return! loop (stage::routes) | |
| Detach(stage) -> return! loop (List.filter (fun x -> x <> stage) routes) | |
} | |
loop []) |
yep, the other functions are not needed in this instance, the other is the one Don recommended. Its from the MSDN documentation...
Did he mention why he recommended it? Is it better within the agent to behave in a more synchronous manner? What about deadlocks? I know those are possible when calling .Result
on a Task
.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I prefer this one, personally. The other's use of
RunSynchronously
would seem to cause problems. Also, why are you passingignore
into the callback? Is the result expected to beunit
?