Transient (computer programming)
In
Examples of applications of the term are described below.
Java
In the
In
X
In the X Window System, a window is said to be transient for another window if it belongs to that other window and may not outlast it: a dialog box, such as an alert message, is a common example. This should not be confused with a window containing another window: contained windows lie entirely within their parents, but transients are separate windows which can generally be moved freely around the screen. Transient windows may be treated specially by the window manager, and unlike top-level windows (which can require user placement, as in twm), must never require any user interaction on appearing.[3]
Operating systems
Transient also refers to a module that, once loaded into main
In the mid-to-late 1960s, mainframe computers, such as the IBM System/360, had memory sizes from 8 KB to 512 KB. In order to conserve memory, transients were small modules that supported a specific task, and were swapped in and out of memory. The concept of transient area is part of Mythical Man-Month's discussion on design and the use of main memory.[5] The operating system for the S/360 had two areas reserved for transients that supported input/output operations. These were referred to as the "logical transient area"[6] and the "physical transient area."[7] If an application program, for example, needed to use the printer, transients that supported printing were brought into the transient areas. If an application needed to use tape drives, transients that supported tape drive access were brought into the transient areas. The IBM 1130 of the same era used part of the first 4K of memory as a transient area.
In the 1980s, MS-DOS reloaded the transient portion of COMMAND.COM between programs or user commands.[8][9]
Message passing
At the level of message passing, transient communication means the way by which the messages are not saved into a buffer to wait for its delivery at the message receiver. The messages will be delivered only if both the systems (sender and receiver) are running. If the receiver is not running at the send time, the message will be discarded, because it has not been stored into intermediate buffers.
References
- ^ Discover the secrets of the Java Serialization API - article from Oracle
- ^ For more detail go to: Jboss.org
- ^ "ICCCM - Client to Window Manager Communication". Tronche.com. Retrieved 2014-03-20.
- ^ William Stallings, Sistemas Operativos, 5th edition (2005), Page 311
- ISBN 0-201-00650-2.
- ^ 1200 bytes, for IOCS functions such as OPEN and CLOSE
- ^ 556 bytes, for device error handling
- ^ "The MS-DOS Encyclopeida".
- PC Magazine. pp. 349–352.