Skip to content

Commit c685e80

Browse files
committed
cleaning up some text on websockets page
1 parent 7ac7173 commit c685e80

File tree

4 files changed

+10
-10
lines changed

4 files changed

+10
-10
lines changed

all.html

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -4842,9 +4842,9 @@ <h2>Why use WebSockets?</h2>
48424842
applications would implement long polling via frequent
48434843
Asynchronous JavaScript and XML (AJAX) requests as shown in the below diagram. </p>
48444844
<p><img src="theme/img/ajax-long-polling.png" width="100%" alt="Long polling via AJAX is incredibly inefficient for some applications." class="technical-diagram" /></p>
4845-
<p>Server push, as shown in the below diagram, is more efficient and scalable
4846-
than long polling because the web browser does not have to constantly ask for
4847-
updates through a stream of AJAX requests.</p>
4845+
<p>Server push is more efficient and scalable than long polling because the
4846+
web browser does not have to constantly ask for updates through a stream
4847+
of AJAX requests.</p>
48484848
<p><img src="theme/img/websockets-flow.png" width="100%" alt="WebSockets are more efficient than long polling for server sent updates." class="technical-diagram" /></p>
48494849
<p>The WebSockets approach for server pushed updates works well for certain
48504850
categories of web applications such as chat room, which is why that's often

feeds/all.atom.xml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,2 +1,2 @@
11
<?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-01-25T12:42:28Z</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-01-25T14:27:01Z</updated></feed>

source/content/pages/12-next/1201-websockets.markdown

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -38,9 +38,9 @@ Asynchronous JavaScript and XML (AJAX) requests as shown in the below diagram.
3838

3939
<img src="theme/img/ajax-long-polling.png" width="100%" alt="Long polling via AJAX is incredibly inefficient for some applications." class="technical-diagram" />
4040

41-
Server push, as shown in the below diagram, is more efficient and scalable
42-
than long polling because the web browser does not have to constantly ask for
43-
updates through a stream of AJAX requests.
41+
Server push is more efficient and scalable than long polling because the
42+
web browser does not have to constantly ask for updates through a stream
43+
of AJAX requests.
4444

4545
<img src="theme/img/websockets-flow.png" width="100%" alt="WebSockets are more efficient than long polling for server sent updates." class="technical-diagram" />
4646

websockets.html

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -56,9 +56,9 @@ <h2>Why use WebSockets?</h2>
5656
applications would implement long polling via frequent
5757
Asynchronous JavaScript and XML (AJAX) requests as shown in the below diagram. </p>
5858
<p><img src="theme/img/ajax-long-polling.png" width="100%" alt="Long polling via AJAX is incredibly inefficient for some applications." class="technical-diagram" /></p>
59-
<p>Server push, as shown in the below diagram, is more efficient and scalable
60-
than long polling because the web browser does not have to constantly ask for
61-
updates through a stream of AJAX requests.</p>
59+
<p>Server push is more efficient and scalable than long polling because the
60+
web browser does not have to constantly ask for updates through a stream
61+
of AJAX requests.</p>
6262
<p><img src="theme/img/websockets-flow.png" width="100%" alt="WebSockets are more efficient than long polling for server sent updates." class="technical-diagram" /></p>
6363
<p>The WebSockets approach for server pushed updates works well for certain
6464
categories of web applications such as chat room, which is why that's often

0 commit comments

Comments
 (0)