This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
pergamonmystic:linkedhelp:patience [2021/09/29 11:09] admin |
pergamonmystic:linkedhelp:patience [2021/09/29 11:14] (current) admin |
||
---|---|---|---|
Line 13: | Line 13: | ||
==== Desktop vs. Online ==== | ==== Desktop vs. Online ==== | ||
- | In a **desktop application**, all activity taking place is within the memory of the computer on which you are working - and computer memory is //extremely// fast. The biggest impacts on speed which you will encounter in this environment is data access to a hard-disk, which is still largely a mechanical device and therefore is extremely slow by comparison; and, redrawing the screen when a long process is being undertaken. In this latter case the speed delay is not because the display is slow, but because operating systems typically regard screen updates to be the least important of all of the actions being undertaken (i.e. the //process// of adding 2+2 is regarded as more important than updating the screen to //tell you// how it is being done). | + | In a **desktop application**, all activity taking place is within the memory of the computer on which you are working - and computer memory is //extremely// fast. The biggest impacts on speed which you will encounter in this environment is data access to a hard-disk, which is still largely a mechanical device and therefore is extremely slow by comparison; and, redrawing the screen when a long process is being undertaken. In this latter case the speed delay is not because the display is slow, but because operating systems typically regard screen updates to be the least important of all of the actions being undertaken (i.e. the //process// of adding 2+2 is regarded as more important than updating the screen to //tell you// how it is being done). Screen updates therefore take place all at once, when all of the work is done. |
In an **online application**, activity takes place in a mixture of your local Internet Browser (which may be MS Edge, Opera, Chrome, Safari, Brave etc.), and the server on which the application is running. Local activities will remain extremely fast, such as the operation of common on-screen controls like text boxes, buttons, sliders etc. Activities taking place on the server are also extremely fast, as the server is usually an even bigger, faster and more powerful machine than the one that you are working on. | In an **online application**, activity takes place in a mixture of your local Internet Browser (which may be MS Edge, Opera, Chrome, Safari, Brave etc.), and the server on which the application is running. Local activities will remain extremely fast, such as the operation of common on-screen controls like text boxes, buttons, sliders etc. Activities taking place on the server are also extremely fast, as the server is usually an even bigger, faster and more powerful machine than the one that you are working on. | ||
Line 57: | Line 57: | ||
==== Thing to do / not do when using a Cloud Application ==== | ==== Thing to do / not do when using a Cloud Application ==== | ||
- | In a practical sense, communications speed between the browser and the server actually impact only one thing - //user perception//. | + | In a practical sense, communications speed between the browser and the server actually impact only one thing - **//user perception//**. |
- | While computers are very fast at performing certain tasks compared to humans, even //extremely small differences// in time are often exaggerated by humans to seem like major delays. | + | While computers are very fast at performing certain tasks compared to humans, even //extremely small differences// in time are often exaggerated by human brains to seem like major delays. |
Gradually, users adjust to how internet based applications work but here are some things to consider: | Gradually, users adjust to how internet based applications work but here are some things to consider: |