Editing 1854: Refresh Types
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 11: | Line 11: | ||
=== Soft refresh === | === Soft refresh === | ||
− | ''Soft refresh'' refers to an operation in a web page | + | ''Soft refresh'' refers to an operation in a web page that requests new information without reloading the entire page. The given example, {{w|Gmail}}, includes a feature that allows users to poll new emails and show it in the inbox interface. It is a command using {{w|JavaScript}} and {{w|Ajax (programming)|Ajax}} to load new contents from the server in the background and only update necessary components of the page. Since modern web applications do this also automatically in short time intervals those buttons are mostly unnecessary. In Gmail a user will see a new message instantly. |
=== Normal refresh === | === Normal refresh === | ||
Line 17: | Line 17: | ||
=== Hard refresh === | === Hard refresh === | ||
− | What Randall calls ''hard refresh'' is a less common browser operation forcing the browser to re-download every part of the | + | What Randall calls ''hard refresh'' is a less common browser operation forcing the browser to re-download every part of the webpage, ignoring any cached content. Caching is a common way of increasing webpage load times. Browsers save resources such us images or {{w|Cascading Style Sheets|CSS stylesheets}} on the first visit on a webpage and use the local copy on subsequent visits. It allows them to decrease amount of transfer needed to show the webpage, but prevents showing changes made to the resources (for example a web developer chanigng the stylesheet). In those cases the ''hard refresh'' ensures that each part of the website is downloaded in its newest form. |
− | If there is a {{w|Proxy server| | + | If there is a {{w|Proxy server|Web-Proxy}} or a Cloud-Cache (like used for this wiki) in between the browser and the Web-Server this type of refreshing may not work. In this case, unless a purge link is available, the user has to wait until the cache entry is expired and a new request to the web server is done. A Web-developer may try to avoid this behaviour by including special meta-tags in the HTML header to suppress caching, but not all proxies or clouds follow these instructions. |
=== Harder refresh === | === Harder refresh === | ||
''Harder refresh'' is a joke that extends the existing naming scheme. The joke is that if a ''hard refresh'' resets the browser display and cache, a ''harder refresh'' should reset the source of the data by cycling power in the data center. Assuming no damage was done, this would reset the memory on the server, erasing any information that had not been written to disk, and setting the server to the state it was in at launch. This would cause considerable downtime, and would be unlikely to help the user at all. | ''Harder refresh'' is a joke that extends the existing naming scheme. The joke is that if a ''hard refresh'' resets the browser display and cache, a ''harder refresh'' should reset the source of the data by cycling power in the data center. Assuming no damage was done, this would reset the memory on the server, erasing any information that had not been written to disk, and setting the server to the state it was in at launch. This would cause considerable downtime, and would be unlikely to help the user at all. | ||
− | In {{w|Orchestration (computing)|orchestrated}} environment it may indirectly cause some virtual machines in the {{w|Cloud computing|cloud}} to be rebooted and assigned to | + | In {{w|Orchestration (computing)|orchestrated}} environment it may indirectly cause some virtual machines in the {{w|Cloud computing|cloud}} to be rebooted and assigned to an other web server needing more workload. But a growing workload is caused by hundreds or thousands additional requests and not just a single key combination from one browser. And rebooting an actual physical server upon a web page request is not possible, unless there is a software or operating system bug that will cause exactly this. |
− | The ''harder refresh'' uses six keys, including the non-standard '[https://askubuntu.com/questions/19558/what-are-the-meta-super-and-hyper-keys HYPER]' key, a feature of the {{w|Space cadet keyboard}} | + | The ''harder refresh'' uses six keys, including the non-standard '[https://askubuntu.com/questions/19558/what-are-the-meta-super-and-hyper-keys HYPER]' key, a feature of the {{w|Space cadet keyboard}}. |
=== Hardest refresh === | === Hardest refresh === | ||
− | The fifth option, ''hardest refresh'', moves beyond resetting the source of the data and resets the entire internet back to {{w|ARPANET}}, an early military network which was a forerunner to the modern internet. The implications of this are not made clear, but it should be noted that it wouldn't help to | + | The fifth option, ''hardest refresh'', moves beyond resetting the source of the data and resets the entire internet back to {{w|ARPANET}}, an early military network which was a forerunner to the modern internet. The implications of this are not made clear, but it should be noted that it wouldn't help to fix any problems a user is experiencing in-browser, as {{w|HTTP}}, the protocol by which web pages are sent, was not developed until late 1990, the year ARPANET was decommissioned. |
− | The ''hardest refresh'' shortcut uses fifteen keys, including non-standard ones such as Ø and ⏏. (The former is a key found on Danish | + | The ''hardest refresh'' shortcut uses fifteen keys, including non-standard ones such as Ø and ⏏. (The former is a key found on Norwegian and Danish keyboards, the latter is the "eject" key found on [older?] Mac keyboards and some laptops.) The shortcut makes amusing comparisons about a shortcut that includes not only the F5 function key, but also the keys for the letter "F" and the digit "5", as well as the similarity in appearance between O, 0, and Ø. |
− | The title text suggests that the inclusion of both the {{w|Windows key}} and {{w|Command key}} in the ''hardest refresh'' shortcut is a security measure akin to the {{w|Two-man rule}}, as it would require two keyboards to enter | + | The title text suggests that the inclusion of both the {{w|Windows key}} and {{w|Command key}} in the ''hardest refresh'' shortcut is a security measure akin to the {{w|Two-man rule}}, as it would require two keyboards to enter. |
==Transcript== | ==Transcript== | ||
− | + | {{incomplete transcript|Do NOT delete this tag too soon. No table is the preferred version, just describe what's in the picture including the special keys.}} | |
− | + | :{| class=wikitable | |
− | + | ! Refresh Type | |
− | + | ! Example Shortcuts | |
− | + | ! Effect | |
− | + | |- | |
− | + | | Soft Refresh | |
− | + | | Gmail <span style="border: 1px solid black">REFRESH</span> Button | |
− | + | | Requests update within JavaScript | |
− | + | |- | |
− | + | | Normal Refresh | |
− | + | | F5, CTRL-R, ⌘R | |
− | + | |Refreshes page | |
− | + | |- | |
− | + | |Hard Refresh | |
− | + | | CTRL-F5, CTRL-⇧, ⌘⇧R | |
− | + | | Refreshes page including cached files | |
− | + | |- | |
− | + | |Harder Refresh | |
− | + | | CTRL-⇧-HYPER-ESC-R-F5 | |
− | + | | Remotely cycles power to datacenter | |
− | + | |- | |
− | + | |Hardest Refresh | |
− | + | | CTRL-⌘<span title="Windows key logo">⊞</span>⇧#-R-F5-F-5-ESC-O-0-Ø-⏏-SCROLL LOCK | |
− | + | | Internet starts over from ARPANET | |
− | + | |} | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
{{comic discussion}} | {{comic discussion}} |