Revert "Unify dart:isolate."

lib/isolate/isolate_dart2js.dart

Index: lib/isolate/isolate_dart2js.dart
diff --git a/lib/isolate/isolate_dart2js.dart b/lib/isolate/isolate_dart2js.dart
new file mode 100644
index 0000000000000000000000000000000000000000..6b2d3d80fd272dc94479a942b81f6e62a764716b
--- /dev/null
+++ b/lib/isolate/isolate_dart2js.dart
@@ -0,0 +1,62 @@
+// Copyright (c) 2012, the Dart project authors.  Please see the AUTHORS file
+// for details. All rights reserved. Use of this source code is governed by a
+// BSD-style license that can be found in the LICENSE file.
+
+
+/**
+ * The `dart:isolate` library defines APIs to spawn and communicate with
+ * isolates.
+ *
+ * All code in dart runs in the context of an isolate. Each isolate has its own
+ * heap, which means that all values in memory, including globals, are available
+ * only to that isolate. The only mechanism available to communicate between
+ * isolates is to pass messages. Messages are sent through ports. This library
+ * defines [ReceivePort] to represent the receiver's end of a communication
+ * channel, and [SendPort] to represent the sender's end.
+ *
+ * All isolates start with an initial receive port, which is set in the
+ * top-level property [port]. This port is used to establish the first
+ * communication between isolates.
+ *
+ * Two APIs are available to spawn a new isolate: [spawnFunction] and
+ * [spawnUri]. [spawnFunction] creates a new isolate that is using the same
+ * source code as the current isolate, [spawnUri] allows spawning an isolate
+ * that was written independently.
+ *
+ * There is currently no way to indicate in the API whether the isolates should
+ * run on the same or different threads. The underlying system will schedule the
+ * isolate were appropriate. In the near future we will add an API to create DOM
+ * isolates. These are isolates that share access to the DOM. All DOM isolates
+ * will run on the UI thread.
+ *
+ * This library is still evolving. New APIs are being added, and some will be
+ * deprecated and removed. In particular, the class [Isolate] will be
+ * deprecated as soon the dartvm has an implementation working for
+ * [spawnFunction] and [spawnUri], and we have an API to spawn DOM isolates.
+ */
+#library("dart:isolate");
+
+#import("dart:uri");
+#source("isolate_api.dart");
+#source("timer.dart");
+#source("timer_hook.dart");
+#source("serialization.dart");
+#source("dart2js/compiler_hooks.dart");
+#source("dart2js/isolateimpl.dart");
+#source("dart2js/messages.dart");
+#source("dart2js/ports.dart");
+#source("dart2js/timer_provider.dart");
+
+/**
+ * Called by the compiler to support switching
+ * between isolates when we get a callback from the DOM.
+ */
+void _callInIsolate(_IsolateContext isolate, Function function) {
+  isolate.eval(function);
+  _globalState.topEventLoop.run();
+}
+
+/**
+ * Called by the compiler to fetch the current isolate context.
+ */
+void _currentIsolate() => _globalState.currentContext;