Transient (computer programming) - Revision history

AIMarTech: /* growthexperiments-addlink-summary-summary:3|0|0 */

2025-04-28T05:32:26Z

Link suggestions feature: 3 links added.

← Previous revision		Revision as of 05:32, 28 April 2025
Line 10:		Line 10:
	==X==		==X==
	[[Image:Dialog1.png\|right\|thumb\|A dialog box is an example of a transient window.]]		[[Image:Dialog1.png\|right\|thumb\|A dialog box is an example of a transient window.]]
	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.<ref>{{cite web\|url=http://tronche.com/gui/x/icccm/sec-4.html \|title=ICCCM - Client to Window Manager Communication \|publisher=Tronche.com \|date= \|accessdate=2014-03-20}}</ref>		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.<ref>{{cite web\|url=http://tronche.com/gui/x/icccm/sec-4.html \|title=ICCCM - Client to Window Manager Communication \|publisher=Tronche.com \|date= \|accessdate=2014-03-20}}</ref>

	==Operating systems==		==Operating systems==
	''Transient'' also refers to a module that, once loaded into main [[Computer storage\|memory]], is expected to remain in memory for a short time. Today, the term is rarely used, and may be obsolete. The term [[Overlay (programming)\|Overlay]] is commonly used instead, and refer to a program module that is brought to memory when it is needed by the running program and then replaced with another when it is no longer needed, so a program had lower memory requirements. Program modules were written to allow different modules to share the same memory region and the main program itself was responsible of exchanging modules between disk and memory as necessary.<ref>William Stallings, ''Sistemas Operativos, 5th edition'' (2005), Page 311</ref>		''Transient'' also refers to a module that, once loaded into main [[Computer storage\|memory]], is expected to remain in memory for a short time. Today, the term is rarely used, and may be obsolete. The term [[Overlay (programming)\|Overlay]] is commonly used instead, and refer to a program module that is brought to memory when it is needed by the running program and then replaced with another when it is no longer needed, so a program had lower memory requirements. Program modules were written to allow different modules to share the same memory region and the main program itself was responsible of exchanging modules between disk and memory as necessary.<ref>William Stallings, ''Sistemas Operativos, 5th edition'' (2005), Page 311</ref>

	In the mid-to-late 1960s, mainframe computers, such as the [[IBM System/360]], had memory sizes from 8 [[Kilobyte\|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 [[The Mythical Man-Month\|Mythical Man-Month]]'s discussion on design and the use of main memory.<ref>{{cite book		In the mid-to-late 1960s, mainframe computers, such as the [[IBM System/360]], had memory sizes from 8 [[Kilobyte\|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 [[The Mythical Man-Month\|Mythical Man-Month]]'s discussion on design and the use of main memory.<ref>{{cite book
	\|title=The Mythical Man-Month \|year=1975 \|page=101		\|title=The Mythical Man-Month \|year=1975 \|page=101
	\|author=F. P. Brooks \|publisher=Addison-Wesley Publishing Company \|isbn=0-201-00650-2}}</ref> The operating system for the S/360 had two areas reserved for [[DOS/360 and successors#Transients\|transients]] that supported input/output operations. These were referred to as the "logical transient area"<ref>1200 bytes, for IOCS functions such as OPEN and CLOSE</ref> and the "physical transient area."<ref>556 bytes, for device error handling</ref> 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.		\|author=F. P. Brooks \|publisher=Addison-Wesley Publishing Company \|isbn=0-201-00650-2}}</ref> The operating system for the S/360 had two areas reserved for [[DOS/360 and successors#Transients\|transients]] that supported input/output operations. These were referred to as the "logical transient area"<ref>1200 bytes, for IOCS functions such as OPEN and CLOSE</ref> and the "physical transient area."<ref>556 bytes, for device error handling</ref> 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.<ref>{{cite web		In the 1980s, [[MS-DOS]] reloaded the transient portion of [[COMMAND.COM]] between programs or user commands.<ref>{{cite web
	\|url=https://www.pcjs.org/documents/books/mspl13/msdos/encyclopedia/section3		\|url=https://www.pcjs.org/documents/books/mspl13/msdos/encyclopedia/section3
	\|title=The MS-DOS Encyclopeida}}</ref><ref>{{cite magazine \|magazine=[[PC Magazine]]		\|title=The MS-DOS Encyclopeida}}</ref><ref>{{cite magazine \|magazine=[[PC Magazine]]

Citation bot: Add: publisher. | Use this bot. Report bugs. | Suggested by VulcanSphere | Category:X Window System | #UCB_Category 48/61

2023-11-20T05:28:24Z

Add: publisher. | Use this bot. Report bugs. | Suggested by VulcanSphere | Category:X Window System | #UCB_Category 48/61

← Previous revision		Revision as of 05:28, 20 November 2023
Line 17:		Line 17:
	In the mid-to-late 1960s, mainframe computers, such as the [[IBM System/360]], had memory sizes from 8 [[Kilobyte\|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 [[The Mythical Man-Month\|Mythical Man-Month]]'s discussion on design and the use of main memory.<ref>{{cite book		In the mid-to-late 1960s, mainframe computers, such as the [[IBM System/360]], had memory sizes from 8 [[Kilobyte\|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 [[The Mythical Man-Month\|Mythical Man-Month]]'s discussion on design and the use of main memory.<ref>{{cite book
	\|title=The Mythical Man-Month \|year=1975 \|page=101		\|title=The Mythical Man-Month \|year=1975 \|page=101
	\|author=F. P. Brooks \|isbn=0-201-00650-2}}</ref> The operating system for the S/360 had two areas reserved for [[DOS/360 and successors#Transients\|transients]] that supported input/output operations. These were referred to as the "logical transient area"<ref>1200 bytes, for IOCS functions such as OPEN and CLOSE</ref> and the "physical transient area."<ref>556 bytes, for device error handling</ref> 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.		\|author=F. P. Brooks \|publisher=Addison-Wesley Publishing Company \|isbn=0-201-00650-2}}</ref> The operating system for the S/360 had two areas reserved for [[DOS/360 and successors#Transients\|transients]] that supported input/output operations. These were referred to as the "logical transient area"<ref>1200 bytes, for IOCS functions such as OPEN and CLOSE</ref> and the "physical transient area."<ref>556 bytes, for device error handling</ref> 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.<ref>{{cite web		In the 1980s, [[MS-DOS]] reloaded the transient portion of COMMAND.COM between programs or user commands.<ref>{{cite web

BattyBot: Removed non-content empty section(s), performed general fixes

2022-12-15T00:20:29Z

Removed non-content empty section(s), performed general fixes

← Previous revision		Revision as of 00:20, 15 December 2022
Line 17:		Line 17:
	In the mid-to-late 1960s, mainframe computers, such as the [[IBM System/360]], had memory sizes from 8 [[Kilobyte\|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 [[The Mythical Man-Month\|Mythical Man-Month]]'s discussion on design and the use of main memory.<ref>{{cite book		In the mid-to-late 1960s, mainframe computers, such as the [[IBM System/360]], had memory sizes from 8 [[Kilobyte\|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 [[The Mythical Man-Month\|Mythical Man-Month]]'s discussion on design and the use of main memory.<ref>{{cite book
	\|title=The Mythical Man-Month \|year=1975 \|page=101		\|title=The Mythical Man-Month \|year=1975 \|page=101
	\|author=F. P. Brooks \|isbn=0-201-00650-2}}</ref> The operating system for the S/360 had two areas reserved for [[DOS/~~360_and_successors~~#Transients\|transients]] that supported input/output operations. These were referred to as the "logical transient area"<ref>1200 bytes, for IOCS functions such as OPEN and CLOSE</ref> and the "physical transient area."<ref>556 bytes, for device error handling</ref> 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.		\|author=F. P. Brooks \|isbn=0-201-00650-2}}</ref> The operating system for the S/360 had two areas reserved for [[DOS/360 and successors#Transients\|transients]] that supported input/output operations. These were referred to as the "logical transient area"<ref>1200 bytes, for IOCS functions such as OPEN and CLOSE</ref> and the "physical transient area."<ref>556 bytes, for device error handling</ref> 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.<ref>{{cite web		In the 1980s, [[MS-DOS]] reloaded the transient portion of COMMAND.COM between programs or user commands.<ref>{{cite web
Line 23:		Line 23:
	\|title=The MS-DOS Encyclopeida}}</ref><ref>{{cite magazine \|magazine=[[PC Magazine]]		\|title=The MS-DOS Encyclopeida}}</ref><ref>{{cite magazine \|magazine=[[PC Magazine]]
	\|title=Examining the MS-DOS Environment		\|title=Examining the MS-DOS Environment
	\|author=Ray Duncan \|date=January 12, 1988 \|pages=~~349-352~~}}</ref>		\|author=Ray Duncan \|date=January 12, 1988 \|pages=349–352}}</ref>

	==Message passing==		==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.		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.

	== See also ==

	==References==		==References==

Liz: Removing link(s) Wikipedia:Articles for deletion/Temporary (2nd nomination) closed as delete (XFDcloser)

2022-10-30T05:20:28Z

Removing link(s) Wikipedia:Articles for deletion/Temporary (2nd nomination) closed as delete (XFDcloser)

← Previous revision		Revision as of 05:20, 30 October 2022
Line 1:		Line 1:
	In [[computer programming]], '''transient''' is a property of any element in the system that is ~~[[Temporary (disambiguation)\|~~temporary]]. The term applies to ''[[transient applications]]'', i.e. software for the [[End user of a computer system\|end-user]] which is displayed with a transient [[application posture]]; ''transient data'', which is discarded after it is no longer needed by the computation; and ''transient code'' which are [[subroutine]]s or [[software component]]s that are loaded in the system only for a fraction of the total [[Run time (program lifecycle phase)\|run time]].		In [[computer programming]], '''transient''' is a property of any element in the system that is temporary. The term applies to ''[[transient applications]]'', i.e. software for the [[End user of a computer system\|end-user]] which is displayed with a transient [[application posture]]; ''transient data'', which is discarded after it is no longer needed by the computation; and ''transient code'' which are [[subroutine]]s or [[software component]]s that are loaded in the system only for a fraction of the total [[Run time (program lifecycle phase)\|run time]].

	Examples of applications of the term are described below.		Examples of applications of the term are described below.
Line 29:		Line 29:

	== See also ==		== See also ==
	* [[Temporary (disambiguation)]]

	==References==		==References==

76.190.38.206: /* Operating systems */ when I read '360' I thought "Xbox" so I specified S/360 in the body

2021-05-04T12:24:56Z

Operating systems: when I read '360' I thought "Xbox" so I specified S/360 in the body

← Previous revision		Revision as of 12:24, 4 May 2021
Line 17:		Line 17:
	In the mid-to-late 1960s, mainframe computers, such as the [[IBM System/360]], had memory sizes from 8 [[Kilobyte\|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 [[The Mythical Man-Month\|Mythical Man-Month]]'s discussion on design and the use of main memory.<ref>{{cite book		In the mid-to-late 1960s, mainframe computers, such as the [[IBM System/360]], had memory sizes from 8 [[Kilobyte\|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 [[The Mythical Man-Month\|Mythical Man-Month]]'s discussion on design and the use of main memory.<ref>{{cite book
	\|title=The Mythical Man-Month \|year=1975 \|page=101		\|title=The Mythical Man-Month \|year=1975 \|page=101
	\|author=F. P. Brooks \|isbn=0-201-00650-2}}</ref> The operating system for the 360 had two areas reserved for [[DOS/360_and_successors#Transients\|transients]] that supported input/output operations. These were referred to as the "logical transient area"<ref>1200 bytes, for IOCS functions such as OPEN and CLOSE</ref> and the "physical transient area."<ref>556 bytes, for device error handling</ref> 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.		\|author=F. P. Brooks \|isbn=0-201-00650-2}}</ref> The operating system for the S/360 had two areas reserved for [[DOS/360_and_successors#Transients\|transients]] that supported input/output operations. These were referred to as the "logical transient area"<ref>1200 bytes, for IOCS functions such as OPEN and CLOSE</ref> and the "physical transient area."<ref>556 bytes, for device error handling</ref> 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.<ref>{{cite web		In the 1980s, [[MS-DOS]] reloaded the transient portion of COMMAND.COM between programs or user commands.<ref>{{cite web

Mandarax: Correct punctuation

2020-08-25T02:48:57Z

Correct punctuation

← Previous revision		Revision as of 02:48, 25 August 2020
Line 19:		Line 19:
	\|author=F. P. Brooks \|isbn=0-201-00650-2}}</ref> The operating system for the 360 had two areas reserved for [[DOS/360_and_successors#Transients\|transients]] that supported input/output operations. These were referred to as the "logical transient area"<ref>1200 bytes, for IOCS functions such as OPEN and CLOSE</ref> and the "physical transient area."<ref>556 bytes, for device error handling</ref> 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.		\|author=F. P. Brooks \|isbn=0-201-00650-2}}</ref> The operating system for the 360 had two areas reserved for [[DOS/360_and_successors#Transients\|transients]] that supported input/output operations. These were referred to as the "logical transient area"<ref>1200 bytes, for IOCS functions such as OPEN and CLOSE</ref> and the "physical transient area."<ref>556 bytes, for device error handling</ref> 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.<ref>{{cite web		In the 1980s, [[MS-DOS]] reloaded the transient portion of COMMAND.COM between programs or user commands.<ref>{{cite web
	\|url=https://www.pcjs.org/documents/books/mspl13/msdos/encyclopedia/section3		\|url=https://www.pcjs.org/documents/books/mspl13/msdos/encyclopedia/section3
	\|title=The MS-DOS Encyclopeida}}</ref><ref>{{cite magazine \|magazine=[[PC Magazine]]		\|title=The MS-DOS Encyclopeida}}</ref><ref>{{cite magazine \|magazine=[[PC Magazine]]

Pi314m: /* Operating systems */ wording

2020-08-24T09:08:12Z

Operating systems: wording

← Previous revision		Revision as of 09:08, 24 August 2020
Line 17:		Line 17:
	In the mid-to-late 1960s, mainframe computers, such as the [[IBM System/360]], had memory sizes from 8 [[Kilobyte\|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 [[The Mythical Man-Month\|Mythical Man-Month]]'s discussion on design and the use of main memory.<ref>{{cite book		In the mid-to-late 1960s, mainframe computers, such as the [[IBM System/360]], had memory sizes from 8 [[Kilobyte\|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 [[The Mythical Man-Month\|Mythical Man-Month]]'s discussion on design and the use of main memory.<ref>{{cite book
	\|title=The Mythical Man-Month \|year=1975 \|page=101		\|title=The Mythical Man-Month \|year=1975 \|page=101
	\|author=F. P. Brooks \|isbn=0-201-00650-2}}</ref> The operating system for the 360 had two areas reserved for [[DOS/360_and_successors#Transients\|transients]] that supported input/output operations. These were referred to as the "logical transient area"<ref>1200 bytes, for IOCS functions such as OPEN and CLOSE</ref> and the "physical transient area."<ref>556 bytes, for device error handling</ref> 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 ~~the~~ part of the 4K of memory as a transient area.		\|author=F. P. Brooks \|isbn=0-201-00650-2}}</ref> The operating system for the 360 had two areas reserved for [[DOS/360_and_successors#Transients\|transients]] that supported input/output operations. These were referred to as the "logical transient area"<ref>1200 bytes, for IOCS functions such as OPEN and CLOSE</ref> and the "physical transient area."<ref>556 bytes, for device error handling</ref> 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.<ref>{{cite web		In the 1980s, [[MS/DOS]] reloaded the transient portion of COMMAND.COM between programs or user commands.<ref>{{cite web

Pi314m: /* Operating systems */ citation

2020-08-24T09:05:16Z

Operating systems: citation

← Previous revision		Revision as of 09:05, 24 August 2020
Line 21:		Line 21:
	In the 1980s, [[MS/DOS]] reloaded the transient portion of COMMAND.COM between programs or user commands.<ref>{{cite web		In the 1980s, [[MS/DOS]] reloaded the transient portion of COMMAND.COM between programs or user commands.<ref>{{cite web
	\|url=https://www.pcjs.org/documents/books/mspl13/msdos/encyclopedia/section3		\|url=https://www.pcjs.org/documents/books/mspl13/msdos/encyclopedia/section3
	\|title=The MS-DOS Encyclopeida}}</ref>		\|title=The MS-DOS Encyclopeida}}</ref><ref>{{cite magazine \|magazine=[[PC Magazine]]
			\|title=Examining the MS-DOS Environment
			\|author=Ray Duncan \|date=January 12, 1988 \|pages=349-352}}</ref>

	==Message passing==		==Message passing==

Pi314m: /* Operating systems */ sizes

2020-08-24T01:16:56Z

Operating systems: sizes

← Previous revision		Revision as of 01:16, 24 August 2020
Line 17:		Line 17:
	In the mid-to-late 1960s, mainframe computers, such as the [[IBM System/360]], had memory sizes from 8 [[Kilobyte\|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 [[The Mythical Man-Month\|Mythical Man-Month]]'s discussion on design and the use of main memory.<ref>{{cite book		In the mid-to-late 1960s, mainframe computers, such as the [[IBM System/360]], had memory sizes from 8 [[Kilobyte\|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 [[The Mythical Man-Month\|Mythical Man-Month]]'s discussion on design and the use of main memory.<ref>{{cite book
	\|title=The Mythical Man-Month \|year=1975 \|page=101		\|title=The Mythical Man-Month \|year=1975 \|page=101
	\|author=F. P. Brooks \|isbn=0-201-00650-2}}</ref> The operating system for the 360 had two areas reserved for [[DOS/360_and_successors#Transients\|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. The [[IBM 1130]] of the same era used the part of the 4K of memory as a transient area.		\|author=F. P. Brooks \|isbn=0-201-00650-2}}</ref> The operating system for the 360 had two areas reserved for [[DOS/360_and_successors#Transients\|transients]] that supported input/output operations. These were referred to as the "logical transient area"<ref>1200 bytes, for IOCS functions such as OPEN and CLOSE</ref> and the "physical transient area."<ref>556 bytes, for device error handling</ref> 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 the part of the 4K of memory as a transient area.

	In the 1980s, [[MS/DOS]] reloaded the transient portion of COMMAND.COM between programs or user commands.<ref>{{cite web		In the 1980s, [[MS/DOS]] reloaded the transient portion of COMMAND.COM between programs or user commands.<ref>{{cite web

Pi314m: /* Operating systems */ 1960 mainframes, 1980s PCs

2020-08-24T00:54:58Z

Operating systems: 1960 mainframes, 1980s PCs

← Previous revision		Revision as of 00:54, 24 August 2020
Line 13:		Line 13:

	==Operating systems==		==Operating systems==
	{{Multiple issues\|section=yes\|
	{{Expert-subject\|Computing\|section\|date=February 2009}}
	{{Refimprove section\|date=December 2006}}
	}}

	''Transient'' also refers to a module that, once loaded into main [[Computer storage\|memory]], is expected to remain in memory for a short time. Today, the term is rarely used, and may be obsolete. The term [[Overlay (programming)\|Overlay]] is commonly used instead, and refer to a program module that is brought to memory when it is needed by the running program and then replaced with another when it is no longer needed, so a program had lower memory requirements. Program modules were written to allow different modules to share the same memory region and the main program itself was responsible of exchanging modules between disk and memory as necessary.<ref>William Stallings, ''Sistemas Operativos, 5th edition'' (2005), Page 311</ref>		''Transient'' also refers to a module that, once loaded into main [[Computer storage\|memory]], is expected to remain in memory for a short time. Today, the term is rarely used, and may be obsolete. The term [[Overlay (programming)\|Overlay]] is commonly used instead, and refer to a program module that is brought to memory when it is needed by the running program and then replaced with another when it is no longer needed, so a program had lower memory requirements. Program modules were written to allow different modules to share the same memory region and the main program itself was responsible of exchanging modules between disk and memory as necessary.<ref>William Stallings, ''Sistemas Operativos, 5th edition'' (2005), Page 311</ref>

	In the mid-to-late 1960s, mainframe computers, such as the [[IBM System/360]], had memory sizes from 8 [[Kilobyte\|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 [[DOS/360_and_successors#Transients\|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.		In the mid-to-late 1960s, mainframe computers, such as the [[IBM System/360]], had memory sizes from 8 [[Kilobyte\|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 [[The Mythical Man-Month\|Mythical Man-Month]]'s discussion on design and the use of main memory.<ref>{{cite book
			\|title=The Mythical Man-Month \|year=1975 \|page=101
			\|author=F. P. Brooks \|isbn=0-201-00650-2}}</ref> The operating system for the 360 had two areas reserved for [[DOS/360_and_successors#Transients\|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. The [[IBM 1130]] of the same era used the part of the 4K of memory as a transient area.

			In the 1980s, [[MS/DOS]] reloaded the transient portion of COMMAND.COM between programs or user commands.<ref>{{cite web
			\|url=https://www.pcjs.org/documents/books/mspl13/msdos/encyclopedia/section3
			\|title=The MS-DOS Encyclopeida}}</ref>

	==Message passing==		==Message passing==

← Previous revision		Revision as of 05:32, 28 April 2025
Line 10:		Line 10:
	==X==		==X==
	[[Image:Dialog1.png\|right\|thumb\|A dialog box is an example of a transient window.]]		[[Image:Dialog1.png\|right\|thumb\|A dialog box is an example of a transient window.]]
	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.<ref>{{cite web\|url=http://tronche.com/gui/x/icccm/sec-4.html \|title=ICCCM - Client to Window Manager Communication \|publisher=Tronche.com \|date= \|accessdate=2014-03-20}}</ref>		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.<ref>{{cite web\|url=http://tronche.com/gui/x/icccm/sec-4.html \|title=ICCCM - Client to Window Manager Communication \|publisher=Tronche.com \|date= \|accessdate=2014-03-20}}</ref>

	==Operating systems==		==Operating systems==
	''Transient'' also refers to a module that, once loaded into main [[Computer storage\|memory]], is expected to remain in memory for a short time. Today, the term is rarely used, and may be obsolete. The term [[Overlay (programming)\|Overlay]] is commonly used instead, and refer to a program module that is brought to memory when it is needed by the running program and then replaced with another when it is no longer needed, so a program had lower memory requirements. Program modules were written to allow different modules to share the same memory region and the main program itself was responsible of exchanging modules between disk and memory as necessary.<ref>William Stallings, ''Sistemas Operativos, 5th edition'' (2005), Page 311</ref>		''Transient'' also refers to a module that, once loaded into main [[Computer storage\|memory]], is expected to remain in memory for a short time. Today, the term is rarely used, and may be obsolete. The term [[Overlay (programming)\|Overlay]] is commonly used instead, and refer to a program module that is brought to memory when it is needed by the running program and then replaced with another when it is no longer needed, so a program had lower memory requirements. Program modules were written to allow different modules to share the same memory region and the main program itself was responsible of exchanging modules between disk and memory as necessary.<ref>William Stallings, ''Sistemas Operativos, 5th edition'' (2005), Page 311</ref>

	In the mid-to-late 1960s, mainframe computers, such as the [[IBM System/360]], had memory sizes from 8 [[Kilobyte\|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 [[The Mythical Man-Month\|Mythical Man-Month]]'s discussion on design and the use of main memory.<ref>{{cite book		In the mid-to-late 1960s, mainframe computers, such as the [[IBM System/360]], had memory sizes from 8 [[Kilobyte\|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 [[The Mythical Man-Month\|Mythical Man-Month]]'s discussion on design and the use of main memory.<ref>{{cite book
	\|title=The Mythical Man-Month \|year=1975 \|page=101		\|title=The Mythical Man-Month \|year=1975 \|page=101
	\|author=F. P. Brooks \|publisher=Addison-Wesley Publishing Company \|isbn=0-201-00650-2}}</ref> The operating system for the S/360 had two areas reserved for [[DOS/360 and successors#Transients\|transients]] that supported input/output operations. These were referred to as the "logical transient area"<ref>1200 bytes, for IOCS functions such as OPEN and CLOSE</ref> and the "physical transient area."<ref>556 bytes, for device error handling</ref> 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.		\|author=F. P. Brooks \|publisher=Addison-Wesley Publishing Company \|isbn=0-201-00650-2}}</ref> The operating system for the S/360 had two areas reserved for [[DOS/360 and successors#Transients\|transients]] that supported input/output operations. These were referred to as the "logical transient area"<ref>1200 bytes, for IOCS functions such as OPEN and CLOSE</ref> and the "physical transient area."<ref>556 bytes, for device error handling</ref> 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.<ref>{{cite web		In the 1980s, [[MS-DOS]] reloaded the transient portion of [[COMMAND.COM]] between programs or user commands.<ref>{{cite web
	\|url=https://www.pcjs.org/documents/books/mspl13/msdos/encyclopedia/section3		\|url=https://www.pcjs.org/documents/books/mspl13/msdos/encyclopedia/section3
	\|title=The MS-DOS Encyclopeida}}</ref><ref>{{cite magazine \|magazine=[[PC Magazine]]		\|title=The MS-DOS Encyclopeida}}</ref><ref>{{cite magazine \|magazine=[[PC Magazine]]