adding new link to websockets page

mattmakai · mattmakai · commit eb9896930a9a · 2015-02-02T14:43:40.000-05:00
diff --git a/all.html b/all.html
@@ -4906,12 +4906,13 @@ <h2>Implementing WebSockets</h2>
 server-side implementation.</p>
 <p>On the client side, it is not necessary to use a JavaScript library for 
 WebSockets. Web browsers that implement WebSockets will expose all necessary
-client-side functionality through the WebSockets object. However, a JavaScript 
-wrapper library can make a developer's life easier by implementing graceful 
-degradation (often falling back to long-polling when WebSockets are 
-not supported) and by providing a wrapper around browser-specific WebSocket 
-quirks. Examples of JavaScript client libraries and WSGI implementations 
-are found below.</p>
+client-side functionality through the 
+<a href="http://www.w3.org/TR/2011/WD-websockets-20110419/">WebSockets object</a>. </p>
+<p>However, a JavaScript wrapper library can make a developer's life easier by 
+implementing graceful degradation (often falling back to long-polling when 
+WebSockets are not supported) and by providing a wrapper around 
+browser-specific WebSocket quirks. Examples of JavaScript client libraries 
+and WSGI implementations are found below.</p>
 <h2>JavaScript client libraries</h2>
 <ul>
 <li>
diff --git a/feeds/all.atom.xml b/feeds/all.atom.xml
@@ -1,2 +1,2 @@
 <?xml version="1.0" encoding="utf-8"?>
-<feed xmlns="http://www.w3.org/2005/Atom"><title>Matt Makai</title><link href="http://www.fullstackpython.com/" rel="alternate"></link><link href="http://www.fullstackpython.com/feeds/all.atom.xml" rel="self"></link><id>http://www.fullstackpython.com/</id><updated>2015-02-02T13:44:08Z</updated></feed>
+<feed xmlns="http://www.w3.org/2005/Atom"><title>Matt Makai</title><link href="http://www.fullstackpython.com/" rel="alternate"></link><link href="http://www.fullstackpython.com/feeds/all.atom.xml" rel="self"></link><id>http://www.fullstackpython.com/</id><updated>2015-02-02T14:43:31Z</updated></feed>
diff --git a/source/content/pages/04-web-development/1201-websockets.markdown b/source/content/pages/04-web-development/1201-websockets.markdown
@@ -71,12 +71,14 @@ server-side implementation.
 
 On the client side, it is not necessary to use a JavaScript library for 
 WebSockets. Web browsers that implement WebSockets will expose all necessary
-client-side functionality through the WebSockets object. However, a JavaScript 
-wrapper library can make a developer's life easier by implementing graceful 
-degradation (often falling back to long-polling when WebSockets are 
-not supported) and by providing a wrapper around browser-specific WebSocket 
-quirks. Examples of JavaScript client libraries and WSGI implementations 
-are found below.
+client-side functionality through the 
+[WebSockets object](http://www.w3.org/TR/2011/WD-websockets-20110419/). 
+
+However, a JavaScript wrapper library can make a developer's life easier by 
+implementing graceful degradation (often falling back to long-polling when 
+WebSockets are not supported) and by providing a wrapper around 
+browser-specific WebSocket quirks. Examples of JavaScript client libraries 
+and WSGI implementations are found below.
 
 
 ## JavaScript client libraries
diff --git a/websockets.html b/websockets.html
@@ -79,12 +79,13 @@ <h2>Implementing WebSockets</h2>
 server-side implementation.</p>
 <p>On the client side, it is not necessary to use a JavaScript library for 
 WebSockets. Web browsers that implement WebSockets will expose all necessary
-client-side functionality through the WebSockets object. However, a JavaScript 
-wrapper library can make a developer's life easier by implementing graceful 
-degradation (often falling back to long-polling when WebSockets are 
-not supported) and by providing a wrapper around browser-specific WebSocket 
-quirks. Examples of JavaScript client libraries and WSGI implementations 
-are found below.</p>
+client-side functionality through the 
+<a href="http://www.w3.org/TR/2011/WD-websockets-20110419/">WebSockets object</a>. </p>
+<p>However, a JavaScript wrapper library can make a developer's life easier by 
+implementing graceful degradation (often falling back to long-polling when 
+WebSockets are not supported) and by providing a wrapper around 
+browser-specific WebSocket quirks. Examples of JavaScript client libraries 
+and WSGI implementations are found below.</p>
 <h2>JavaScript client libraries</h2>
 <ul>
 <li>

Original file line number	Diff line number	Diff line change
`@@ -1,2 +1,2 @@`
`1`	`1`	`<?xml version="1.0" encoding="utf-8"?>`
`2`		`-<feed xmlns="http://www.w3.org/2005/Atom"><title>Matt Makai</title><link href="http://www.fullstackpython.com/" rel="alternate"></link><link href="http://www.fullstackpython.com/feeds/all.atom.xml" rel="self"></link><id>http://www.fullstackpython.com/</id><updated>2015-02-02T13:44:08Z</updated></feed>`
	`2`	`+<feed xmlns="http://www.w3.org/2005/Atom"><title>Matt Makai</title><link href="http://www.fullstackpython.com/" rel="alternate"></link><link href="http://www.fullstackpython.com/feeds/all.atom.xml" rel="self"></link><id>http://www.fullstackpython.com/</id><updated>2015-02-02T14:43:31Z</updated></feed>`