pkg/analysis_server/doc/api.html - Issue 872633002: Use 'print' to send responses/notifications to the client.

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Unified Diff: pkg/analysis_server/doc/api.html

Issue 872633002: Use 'print' to send responses/notifications to the client. (Closed) Base URL: https://dart.googlecode.com/svn/branches/bleeding_edge/dart

Patch Set: Use non-blocking 'stdout', revert 'print' changes. Created 5 years, 11 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

View side-by-side diff with in-line comments

Download patch

« no previous file with comments | « editor/tools/plugins/com.google.dart.server/src/com/google/dart/server/internal/remote/ByteResponseStream.java ('k') | pkg/analysis_server/lib/src/channel/byte_stream_channel.dart » ('j') | pkg/analysis_server/lib/src/channel/byte_stream_channel.dart » ('J')
Expand Comments ('e') | Collapse Comments ('c') | Hide Comments ('s')

Index: pkg/analysis_server/doc/api.html

diff --git a/pkg/analysis_server/doc/api.html b/pkg/analysis_server/doc/api.html

index a4abcfc83078e433f8b36cd0a43c37858d122f0f..69af5fb7e9a0cfc82b708f49238e864d557061c1 100644

--- a/pkg/analysis_server/doc/api.html

+++ b/pkg/analysis_server/doc/api.html

@@ -70,6 +70,10 @@ dt.typeDefinition {

for readability.

</p>

<p>

+ It is the client's responsibility to read output from the server to

+ avoid its blocking.

+ </p>

+ <p>

To ease interoperability with Lisp-based clients (which may not

be able to easily distinguish between empty lists, empty maps,

and null), client-to-server communication is allowed to replace