| commit | c65ac1db19d10035bc08bb8adcc2ec4514df2913 | [log] [tgz] |
|---|---|---|
| author | Lasse R.H. Nielsen <lrn@google.com> | Wed Mar 18 09:54:30 2015 +0100 |
| committer | Lasse R.H. Nielsen <lrn@google.com> | Wed Mar 18 09:54:30 2015 +0100 |
| tree | 6223b8c6767338a338d2fe0d882335abeb93397a | |
| parent | deff8268aac68f7cbfd59b45b9b04299f5609d2c [diff] |
Update Isolate package. No longer contains FunctionRef class since implementations can now send functions. Enable error/done listening on the isolate now that the VM implements it. Add a new abstraction to ports.dart, the "SingleResponseChannel", which is like the other features in that it creates a Future and a SendPort and forwards the first value from the SendPort to the Future. This one exposes the two values as an object with two getters instead of returning one and calling a callback with the other. Clean up some formatting suggested by formatter (but far from all). R=sgjesse@google.com Review URL: https://codereview.chromium.org//1012053002
The isolate package helps with isolates and isolate communication.
The package contains individual libraries with different purposes.
The “ports.dart” sub-library contains functionality for creating SendPorts and reacting to values sent to those ports.
The “isolaterunner.dart” sub-library introduces an IsolateRunner class that gives easy access to the Isolate functionality, and also gives a way to run new functions in the isolate repeatedly, instead of just on the initial spawn call.
The “registry.dart” sub-library provides a way to create an object registry, and give access to it accross different isolates.
The “loadbalancer.dart” sub-library can manage multiple Runner objects, including IsolateRunner, and run functions on the currently least loaded runner.
Please file feature requests and bugs at the issue tracker.