Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(67)

Side by Side 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 unified diff | Download patch | Annotate | Revision Log
OLDNEW
1 <html><head> 1 <html><head>
2 <meta charset="UTF-8"> 2 <meta charset="UTF-8">
3 <title>Analysis Server API Specification</title> 3 <title>Analysis Server API Specification</title>
4 <style>body { 4 <style>body {
5 font-family: sans-serif, serif; 5 font-family: sans-serif, serif;
6 padding-left: 5%; 6 padding-left: 5%;
7 padding-right: 5%; 7 padding-right: 5%;
8 } 8 }
9 h1 { 9 h1 {
10 text-align: center; 10 text-align: center;
(...skipping 52 matching lines...) Expand 10 before | Expand all | Expand 10 after
63 using UTF-8. 63 using UTF-8.
64 </p> 64 </p>
65 <p> 65 <p>
66 When character streams are used as the transport, messages are 66 When character streams are used as the transport, messages are
67 delineated by newlines. This means, in particular, that the JSON 67 delineated by newlines. This means, in particular, that the JSON
68 encoding process must not introduce newlines within a 68 encoding process must not introduce newlines within a
69 message. Note however that newlines are used in this document 69 message. Note however that newlines are used in this document
70 for readability. 70 for readability.
71 </p> 71 </p>
72 <p> 72 <p>
73 It is the client's responsibility to read output from the server to
74 avoid its blocking.
75 </p>
76 <p>
73 To ease interoperability with Lisp-based clients (which may not 77 To ease interoperability with Lisp-based clients (which may not
74 be able to easily distinguish between empty lists, empty maps, 78 be able to easily distinguish between empty lists, empty maps,
75 and null), client-to-server communication is allowed to replace 79 and null), client-to-server communication is allowed to replace
76 any instance of “<tt>{}</tt>” or “<tt>[]</tt>” with null. The 80 any instance of “<tt>{}</tt>” or “<tt>[]</tt>” with null. The
77 server will always properly represent empty lists as 81 server will always properly represent empty lists as
78 “<tt>[]</tt>” and empty maps as “<tt>{}</tt>”. 82 “<tt>[]</tt>” and empty maps as “<tt>{}</tt>”.
79 </p> 83 </p>
80 <h3>Communication Structure</h3> 84 <h3>Communication Structure</h3>
81 <p> 85 <p>
82 Clients can make a request of the server and the server will 86 Clients can make a request of the server and the server will
(...skipping 3572 matching lines...) Expand 10 before | Expand all | Expand 10 after
3655 <p> 3659 <p>
3656 This section contains a list of all of the errors that are 3660 This section contains a list of all of the errors that are
3657 produced by the server and the data that is returned with each. 3661 produced by the server and the data that is returned with each.
3658 </p> 3662 </p>
3659 <p> 3663 <p>
3660 TBD 3664 TBD
3661 </p> 3665 </p>
3662 3666
3663 3667
3664 </body></html> 3668 </body></html>
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698