Added intro to socket API reference docs.

Added intro to socket API reference docs.

Also improved Network Communications documentation:

* removed experimental references
* enhanced permissions to include new socket permission rules.

I don't have a staged version of the docs up and running yet for new server. I've checked the docs locally though.

local commit


BUG=

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=154553

[miket_OOO, 2012-08-31 22:33:59]

LGTM. A few nits on the permissions. Charles, will you have a look at that part,
too, and make sure it matches your understanding?

https://chromiumcodereview.appspot.com/10908045/diff/2001/chrome/common/exten...
File chrome/common/extensions/docs/server2/templates/articles/app_network.html
(right):

https://chromiumcodereview.appspot.com/10908045/diff/2001/chrome/common/exten...
chrome/common/extensions/docs/server2/templates/articles/app_network.html:58:
<li>"tcp-connect:*:23" &ndash; For connecting port 23 of any hosts</li>
connecting to (or maybe on)

https://chromiumcodereview.appspot.com/10908045/diff/2001/chrome/common/exten...
chrome/common/extensions/docs/server2/templates/articles/app_network.html:60:
For connecting port 23 of <em>www.example.com</em></li>
Overall I'd eliminate the "for" from each of these, as it doesn't sound quite
idiomatic. "Connect to www.example.com on port 23" is the right pattern.

https://chromiumcodereview.appspot.com/10908045/diff/2001/chrome/common/exten...
chrome/common/extensions/docs/server2/templates/articles/app_network.html:62:
<li>"udp-send-to::99" &ndash; For sending UDP package to port 99 of any
hosts</li>
packet, not package, and I'd say "sending UDP packets" (plural)

https://chromiumcodereview.appspot.com/10908045/diff/2001/chrome/common/exten...
chrome/common/extensions/docs/server2/templates/articles/app_network.html:64:
<li>"tcp-listen::8080" &ndash; For tcp listening on local port 8080</li>
TCP

[mkearney1, 2012-08-31 23:32:12]

https://chromiumcodereview.appspot.com/10908045/diff/2001/chrome/common/exten...
File chrome/common/extensions/docs/server2/templates/articles/app_network.html
(right):

https://chromiumcodereview.appspot.com/10908045/diff/2001/chrome/common/exten...
chrome/common/extensions/docs/server2/templates/articles/app_network.html:58:
<li>"tcp-connect:*:23" &ndash; For connecting port 23 of any hosts</li>
On 2012/08/31 22:33:59, miket wrote:
> connecting to (or maybe on)

Done.

https://chromiumcodereview.appspot.com/10908045/diff/2001/chrome/common/exten...
chrome/common/extensions/docs/server2/templates/articles/app_network.html:60:
For connecting port 23 of <em>www.example.com</em></li>
On 2012/08/31 22:33:59, miket wrote:
> Overall I'd eliminate the "for" from each of these, as it doesn't sound quite
> idiomatic. "Connect to http://www.example.com on port 23" is the right
pattern.

Done.

https://chromiumcodereview.appspot.com/10908045/diff/2001/chrome/common/exten...
chrome/common/extensions/docs/server2/templates/articles/app_network.html:62:
<li>"udp-send-to::99" &ndash; For sending UDP package to port 99 of any
hosts</li>
On 2012/08/31 22:33:59, miket wrote:
> packet, not package, and I'd say "sending UDP packets" (plural)

Done.

https://chromiumcodereview.appspot.com/10908045/diff/2001/chrome/common/exten...
chrome/common/extensions/docs/server2/templates/articles/app_network.html:64:
<li>"tcp-listen::8080" &ndash; For tcp listening on local port 8080</li>
On 2012/08/31 22:33:59, miket wrote:
> TCP

Done.

[battre, 2012-09-03 13:35:37]

Please do another iteration.

https://chromiumcodereview.appspot.com/10908045/diff/5001/chrome/common/exten...
File chrome/common/extensions/docs/server2/templates/articles/app_network.html
(right):

https://chromiumcodereview.appspot.com/10908045/diff/5001/chrome/common/exten...
chrome/common/extensions/docs/server2/templates/articles/app_network.html:10: <a
href="socket.html">Sockets API</a>.
Socket API (without s)

https://chromiumcodereview.appspot.com/10908045/diff/5001/chrome/common/exten...
chrome/common/extensions/docs/server2/templates/articles/app_network.html:49:
&lt;host> := '*' | '*.' &lt;anychar except '/' and '*'>+
Is this precise? www.example.com would not comply to '*.' &lt;anychar except '/'
and '*'>+

https://chromiumcodereview.appspot.com/10908045/diff/5001/chrome/common/exten...
chrome/common/extensions/docs/server2/templates/articles/app_network.html:82:
</pre>
Add an example how you check for errors in onConnectedCallback? Do you use
chrome.extension.lastError?

https://chromiumcodereview.appspot.com/10908045/diff/5001/chrome/common/exten...
chrome/common/extensions/docs/server2/templates/articles/app_network.html:128:
chrome.socket.create('udp', '127.0.0.1', 1337, {},
Does this open a socket for incoming traffic *from the net*? Or does it only
bind to the loopback device, which is not accessible from anywhere but my
computer?

https://chromiumcodereview.appspot.com/10908045/diff/5001/chrome/common/exten...
chrome/common/extensions/docs/server2/templates/articles/app_network.html:128:
chrome.socket.create('udp', '127.0.0.1', 1337, {},
This is incorrect. create does not take the IP address and port as separate
parameters.

https://chromiumcodereview.appspot.com/10908045/diff/5001/chrome/common/exten...
chrome/common/extensions/docs/server2/templates/articles/app_network.html:128:
chrome.socket.create('udp', '127.0.0.1', 1337, {},
socket.create() takes a CreateOptions parameter but there is no place that
describes the content of this dictionary.

https://chromiumcodereview.appspot.com/10908045/diff/5001/chrome/common/exten...
chrome/common/extensions/docs/server2/templates/articles/app_network.html:129:
function(socketInfo) {
Error handling?

https://chromiumcodereview.appspot.com/10908045/diff/5001/chrome/common/exten...
chrome/common/extensions/docs/server2/templates/articles/app_network.html:132:
chrome.socket.connect(socketId, function(result) {
This is wrong: connect takes an IP address and port as paramters.

https://chromiumcodereview.appspot.com/10908045/diff/5001/chrome/common/exten...
chrome/common/extensions/docs/server2/templates/articles/app_network.html:157:
var data = chrome.socket.read(d.socketId);
This is incorrect: Read uses a callback function.

https://chromiumcodereview.appspot.com/10908045/diff/5001/chrome/common/exten...
chrome/common/extensions/docs/server2/templates/articles/app_network.html:162:
chrome.socket.create('udp', '127.0.0.1', 1337, { onEvent: handleDataEvent },
This is incorrect. create does not take the IP address and port as separate
parameters.

https://chromiumcodereview.appspot.com/10908045/diff/5001/chrome/common/exten...
chrome/common/extensions/docs/server2/templates/articles/app_network.html:162:
chrome.socket.create('udp', '127.0.0.1', 1337, { onEvent: handleDataEvent },
Don't you need to bind() the socket for incoming data? The API documentation
states at the moment that bind() does not support UDP.