Shoeshining


In tape backup, shoeshining (also known as backhitching) is the repeated back and forth motion a tape drive makes when there is interruption in the data stream.
When data is sent to tape, it needs to flow at the same speed the tape is running. If there is a mismatch between speeds, the tape drive will try to accommodate it. For instance, if abackup server is sending data slower than the tape drive processor writes it, the drive will periodically stop and wait for data to catch up. Once the drive determines there is enough data to start writing again, it will rewind to the exact place where the last write took place, reset the tape heads and continue. All this happens very quickly; to the casual observer, the wheels on the tape drive just seem to stop and jerk back and forth (like someone shining their shoes) before moving forward smoothly again.
Because tape is a medium that requires blocks of information to be recorded or read sequentially, blank spaces are not acceptable. Buffers (temporary storage areas) can help with temporary speed mismatches, but they can fill up or empty when the mismatch is chronic.
Excessive shoeshining indicates there is a problem. Repeated back and forth motion not only causes a degradation of service, it also causes excessive wear and tear on both the tape and the tape drive. To prevent shoe-shining, backup administrators need to strike the right balance between the number and speed of backup tape drives, the amount of data being sent to the tape library and the connectivity between components.

Stateless App


A stateless app is an application program that does not record data generated in one session - such as information about user settings and events that occurred -- for use in the next session with that user. The trend toward cloud computing is driving interest in stateless apps.


In a computing context, "state" can be defined as a set of conditions that exist at a given point in time. A stateful application records information about changes in state caused by events during a session, including those caused by user interaction. That means that the application can call up information that will enable configuration changes and so on to remain consistent from one session to the next. The need to retrieve state information, which may be stored on the client device or a remote server, can increase the demand for bandwidth.


Web apps are usually stateful, as are most of the APIs (application-program interfaces) that interconnect them with other Web apps and services. In a cloud environment, however, it's preferable that apps be stateless for the sake of scalability and portability. Furthermore, many important cloud technologies are not equipped to deal with state data. Amazon, for example, recently announced that it was implementing what it called sticky sessions - a mechanism for passing on state data - because its elastic load balancing (ELB) implementation was found to break stateful apps.

Metro Apps

Metro apps are touch-screen-friendlyapps written especially for Microsoft'sSurface line of tablet computers.
Metro apps are available from the Windows store for use on any computer that runs Windows RT or Windows 8. The apps will work not only on tablet devices, but also on any desktop or notebook computer that uses a keyboard and mouse, provided that the correct OS(operating system) is installed. Microsoft plans to introduce Metro apps to support communications, scheduling, news, weather, sports, financial information, music, videos, books, travel, and other popular consumer activities. In addition, there will be an app for cloud storage.
The original designers of Metro apps based their approach on a perceived consumer demand for apps that are engaging, immersive, interactive, touch-based, and usable in multiple form factors. They are built for a tiled UI (user interface) with limited, intuitive, functional graphics. Metro apps are based on the Metro design language, originally conceived for mobile Internet devices (MID) and smartphones.

Sideloading

Sideloading is the installation of an application on a mobile device without using the device's official application-distribution method.

Sideloading works differently on different mobile platforms. To enable sideloading on an Android OS device, for example, the end user simply checks a box in the operating system settings. On an Apple iOS device, however, the end user must jailbreakthe device to enable sideloading. Once sideloading is enabled, the user can download and install applications from any website or third-party app store.

Sideloading offers mobile device users a way to access more applications than are available through commercial app stores such as Google Play or the Apple App Store, but it is important for the end user to understand there can be risks. Commercial app stores screen for malware and other threats and assume responsibility for digital rights management (DRM). Applications from other sources may not have been screened for malware and may be pirated.