Basic communication protocol for server

pkg/analysis_server/test/mocks.dart

Index: pkg/analysis_server/test/mocks.dart
diff --git a/pkg/analysis_server/test/mocks.dart b/pkg/analysis_server/test/mocks.dart
new file mode 100644
index 0000000000000000000000000000000000000000..18f3d6e9d4e9acb129d0bc0a979c6392521b8e4e
--- /dev/null
+++ b/pkg/analysis_server/test/mocks.dart
@@ -0,0 +1,17 @@
+// Copyright (c) 2014, 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.
+
+library mocks;
+
+import '../lib/src/channel.dart';

[devoncarew, 2014/01/20 22:35:01]

You can also use a self-reference here:

import 'package:analysis_server/src/channel.dart';

There's no real semantic difference.

[Brian Wilkerson, 2014/01/21 03:21:20]

That does seem somewhat cleaner, though. What's the prefered style for imports
such as

import 'protocol.dart';

(such as the one in channel.dart)? Should it be

import 'package:analysis_server/src/protocol.dart';

Done.

[devoncarew, 2014/01/21 04:16:08]

Within lib, I've only ever used relative file references. When referencing into
lib (from test, bin, web, ...) I generally use self references.

+
+/**
+ * Instances of the class [MockChannel] implement a [CommunicationChannel] that
+ * does nothing in response to every method invoked on it.
+ */
+class MockChannel implements CommunicationChannel {
+  dynamic noSuchMethod(Invocation invocation) {
+    // Do nothing
+  }
+}