Merge pull request Farata#100 from gAmUssA/master

addressing editors' questions for ch9
n3ur0n · Dec 2, 2013 · 365d8fa · 365d8fa
2 parents bfcda31 + b2abbd7
commit 365d8fa
Show file tree

Hide file tree

Showing 5 changed files with 93 additions and 62 deletions.
diff --git a/Vik_comments_to_editor.adoc b/Vik_comments_to_editor.adoc
@@ -39,4 +39,17 @@ from +Chapters 10-12.pdf+ document
 from +Chapters 10-12.pdf+ document
 
 * p. 359 inconsistency addressed in a favor of JSHint.
-* p. 396 I don't understand what editor meant here.
+* p. 396 I don't understand what editor meant here.
+
+== Chapter 9
+
+* p. 403 these tree subsections describe existing architectural styles achieving or emulating same aim - bidirectional communications. On the contrary, websocket is a absolutely new protocol that uses http to bootstrap communication.
+* p. 404 explanation follows
+* p. 407 SSE does only server-push. But it's only one way street.
+* p. 408 We don't need to provide any "advanced introduction to IDL". We provide link to wikipedia. IDL not essential to WebSocket. It's just one of the ways to describe APIs.
+* p. 411 Explanation of TCP is out of the scope of this book. In order for readers to understand this section, we can recommend O'reillys book about TCP, HTTP, HTTPs. Magic string is exact (as mentioned).
+* p. 412 I'll stick to my formulationю 
+* p. 418 Yes, csv and psv are still very common formats in enterprises these days
+* p. 420 JSON was extensively covered in ch2. DOn't want to repeat it here.
+* p. 422 ???
+* p. 439 Chrome Developer Tools are availabe on for ... Chrome. Wireshark allows to debug networking in browsers which development tools lack of debugging tools for websocket.