Commit c685e80
File tree
- feeds
- source/content/pages/12-next
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -4842,9 +4842,9 @@ <h2>Why use WebSockets?</h2> | |||
| 4842 | 4842 | applications would implement long polling via frequent | |
| 4843 | 4843 | Asynchronous JavaScript and XML (AJAX) requests as shown in the below diagram. </p> | |
| 4844 | 4844 | <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> | ||
| 4848 | 4848 | <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> | |
| 4849 | 4849 | <p>The WebSockets approach for server pushed updates works well for certain | |
| 4850 | 4850 | categories of web applications such as chat room, which is why that's often | |
| 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-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> | ||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -38,9 +38,9 @@ Asynchronous JavaScript and XML (AJAX) requests as shown in the below diagram. | |||
| 38 | 38 | ||
| 39 | 39 | <img src="theme/img/ajax-long-polling.png" width="100%" alt="Long polling via AJAX is incredibly inefficient for some applications." class="technical-diagram" /> | |
| 40 | 40 | ||
| 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. | ||
| 44 | 44 | ||
| 45 | 45 | <img src="theme/img/websockets-flow.png" width="100%" alt="WebSockets are more efficient than long polling for server sent updates." class="technical-diagram" /> | |
| 46 | 46 | ||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -56,9 +56,9 @@ <h2>Why use WebSockets?</h2> | |||
| 56 | 56 | applications would implement long polling via frequent | |
| 57 | 57 | Asynchronous JavaScript and XML (AJAX) requests as shown in the below diagram. </p> | |
| 58 | 58 | <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> | ||
| 62 | 62 | <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> | |
| 63 | 63 | <p>The WebSockets approach for server pushed updates works well for certain | |
| 64 | 64 | categories of web applications such as chat room, which is why that's often | |
0 commit comments