Transient (computer programming)
From Wikipedia, the free encyclopedia
Contents |
[edit] Programming
[edit] Java
In the Java programming language, transient
is a keyword used as a field modifier. When a field is declared transient, it would not be serialized even if the class to which it belongs is serialized. It must be noted that in Java, methods, classes and interfaces cannot be declared as transient.
In Hibernate, transient describes an object which has been instantiated, but is not associated with a Hibernate session, ie. the object resides in memory but is not being persisted.
For more detail go to: Hibernate.org
[edit] Operating Systems
This article or section is in need of attention from an expert on the subject. Please help recruit one or improve this article yourself. See the talk page for details. Please consider using {{Expert-subject}} to associate this request with a WikiProject |
This article needs additional citations for verification. Please help improve this article by adding reliable references. Unsourced material may be challenged and removed. (December 2006) |
Transient also refers to a module that, once loaded into main memory, is expected to remain in memory for a short time. Today, the term is rarely used, and may be obsolete.
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 operating system for the 360 had two areas reserved for transients that supported input/output operations. These were referred to as the “logical transient area,” and the “physical transient area.” 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.
[edit] 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 deliver at the message receiver. The messages will be delivered only if both the systems (sender and receiver) are running. If, at the send time, the receiver is not running, the message will be discarded, because it has not been saved into intermediate buffers.