Process-oriented programming - Revision history

Mathnerd314159: change paradigms template to navbox (see Template talk:Programming paradigms#too long)

2024-02-01T22:54:40Z

change paradigms template to navbox (see Template talk:Programming paradigms#too long)

← Previous revision		Revision as of 22:54, 1 February 2024
Line 1:		Line 1:
⚫	{{Programming paradigms}}
	'''Process-oriented programming''' is a [[programming paradigm]] that separates the concerns of data structures and the concurrent processes that act upon them. The data structures in this case are typically persistent, complex, and large scale - the subject of general purpose applications, as opposed to specialized processing of specialized data sets seen in high productivity applications (HPC). The model allows the creation of large scale applications that partially share common data sets. Programs are functionally decomposed into parallel processes that create and act upon logically shared data.		'''Process-oriented programming''' is a [[programming paradigm]] that separates the concerns of data structures and the concurrent processes that act upon them. The data structures in this case are typically persistent, complex, and large scale - the subject of general purpose applications, as opposed to specialized processing of specialized data sets seen in high productivity applications (HPC). The model allows the creation of large scale applications that partially share common data sets. Programs are functionally decomposed into parallel processes that create and act upon logically shared data.

Line 21:		Line 20:
	==External links==		==External links==
	* [http://digitalscholarship.unlv.edu/cgi/viewcontent.cgi?article=2392&context=thesesdissertations Sowders, Matthew, "ProcessJ: A process-oriented programming language" (2011). UNLV Theses, Dissertations, Professional Papers, and Capstones. Paper 1393.]		* [http://digitalscholarship.unlv.edu/cgi/viewcontent.cgi?article=2392&context=thesesdissertations Sowders, Matthew, "ProcessJ: A process-oriented programming language" (2011). UNLV Theses, Dissertations, Professional Papers, and Capstones. Paper 1393.]

		⚫	{{Programming paradigms navbox}}

	[[Category:Programming paradigms]]		[[Category:Programming paradigms]]

Citation bot: Alter: template type. | Use this bot. Report bugs. | Suggested by Abductive | Category:Programming paradigms | #UCB_Category 5/113

2021-09-21T11:56:37Z

Alter: template type. | Use this bot. Report bugs. | Suggested by Abductive | Category:Programming paradigms | #UCB_Category 5/113

← Previous revision		Revision as of 11:56, 21 September 2021
Line 4:		Line 4:
	The paradigm was originally invented for parallel computers in the 1980s, especially computers built with [[transputer]] microprocessors by [[INMOS]], or similar architectures. [[Occam programming language\|Occam]] was an early process-oriented language developed for the Transputer.		The paradigm was originally invented for parallel computers in the 1980s, especially computers built with [[transputer]] microprocessors by [[INMOS]], or similar architectures. [[Occam programming language\|Occam]] was an early process-oriented language developed for the Transputer.

	Some derivations have evolved from the [[message passing]] paradigm of Occam to enable uniform efficiency when porting applications between [[distributed memory]] and [[shared memory]] parallel computers {{Citation needed\|date=June 2012}}. The first such derived example appears in the programming language [[Ease programming language\|Ease]] designed at Yale University<ref name="process">{{cite ~~paper~~ \| last=Ericsson-Zenith \| title=Programming with Ease; Semiotic definition of the language\|publisher=Yale University, Computer Science Technical Report YALEU/DCS/RR-809\|year=1990}}</ref><ref name="process2">{{cite book \| last=Ericsson-Zenith \|title=Process Interaction Models\|publisher=Paris University\|year=1992}}</ref> in 1990. Similar models have appeared since in the loose combination of SQL databases and objected oriented languages such as [[Java (programming language)\|Java]], often referred to as object-relational models and widely used in large scale distributed systems today. The paradigm is likely to appear on desktop computers as microprocessors increase the number of processors ([[Multi-core processor\|multicore]]) per chip.		Some derivations have evolved from the [[message passing]] paradigm of Occam to enable uniform efficiency when porting applications between [[distributed memory]] and [[shared memory]] parallel computers {{Citation needed\|date=June 2012}}. The first such derived example appears in the programming language [[Ease programming language\|Ease]] designed at Yale University<ref name="process">{{cite document \| last=Ericsson-Zenith \| title=Programming with Ease; Semiotic definition of the language\|publisher=Yale University, Computer Science Technical Report YALEU/DCS/RR-809\|year=1990}}</ref><ref name="process2">{{cite book \| last=Ericsson-Zenith \|title=Process Interaction Models\|publisher=Paris University\|year=1992}}</ref> in 1990. Similar models have appeared since in the loose combination of SQL databases and objected oriented languages such as [[Java (programming language)\|Java]], often referred to as object-relational models and widely used in large scale distributed systems today. The paradigm is likely to appear on desktop computers as microprocessors increase the number of processors ([[Multi-core processor\|multicore]]) per chip.

	The [[Actor model]] might usefully be described as a specialized kind of process-oriented system in which the message-passing model is restricted to the simple fixed case of one infinite [[input queue]] per process (i.e. actor), to which any other process can send messages.		The [[Actor model]] might usefully be described as a specialized kind of process-oriented system in which the message-passing model is restricted to the simple fixed case of one infinite [[input queue]] per process (i.e. actor), to which any other process can send messages.

Ivtue: Added wikilink to input queue and fixed spelling mistake.

2020-06-27T17:45:09Z

Added wikilink to input queue and fixed spelling mistake.

← Previous revision		Revision as of 17:45, 27 June 2020
Line 6:		Line 6:
	Some derivations have evolved from the [[message passing]] paradigm of Occam to enable uniform efficiency when porting applications between [[distributed memory]] and [[shared memory]] parallel computers {{Citation needed\|date=June 2012}}. The first such derived example appears in the programming language [[Ease programming language\|Ease]] designed at Yale University<ref name="process">{{cite paper \| last=Ericsson-Zenith \| title=Programming with Ease; Semiotic definition of the language\|publisher=Yale University, Computer Science Technical Report YALEU/DCS/RR-809\|year=1990}}</ref><ref name="process2">{{cite book \| last=Ericsson-Zenith \|title=Process Interaction Models\|publisher=Paris University\|year=1992}}</ref> in 1990. Similar models have appeared since in the loose combination of SQL databases and objected oriented languages such as [[Java (programming language)\|Java]], often referred to as object-relational models and widely used in large scale distributed systems today. The paradigm is likely to appear on desktop computers as microprocessors increase the number of processors ([[Multi-core processor\|multicore]]) per chip.		Some derivations have evolved from the [[message passing]] paradigm of Occam to enable uniform efficiency when porting applications between [[distributed memory]] and [[shared memory]] parallel computers {{Citation needed\|date=June 2012}}. The first such derived example appears in the programming language [[Ease programming language\|Ease]] designed at Yale University<ref name="process">{{cite paper \| last=Ericsson-Zenith \| title=Programming with Ease; Semiotic definition of the language\|publisher=Yale University, Computer Science Technical Report YALEU/DCS/RR-809\|year=1990}}</ref><ref name="process2">{{cite book \| last=Ericsson-Zenith \|title=Process Interaction Models\|publisher=Paris University\|year=1992}}</ref> in 1990. Similar models have appeared since in the loose combination of SQL databases and objected oriented languages such as [[Java (programming language)\|Java]], often referred to as object-relational models and widely used in large scale distributed systems today. The paradigm is likely to appear on desktop computers as microprocessors increase the number of processors ([[Multi-core processor\|multicore]]) per chip.

	The [[Actor model]] might usefully be described as a ~~specialised~~ kind of process-oriented system in which the message-passing model is restricted to the simple fixed case of one infinite input queue per process (i.e. actor), to which any other process can send messages.		The [[Actor model]] might usefully be described as a specialized kind of process-oriented system in which the message-passing model is restricted to the simple fixed case of one infinite [[input queue]] per process (i.e. actor), to which any other process can send messages.

	==See also==		==See also==

Jarble: linking

2020-03-20T00:19:04Z

linking

← Previous revision		Revision as of 00:19, 20 March 2020
Line 4:		Line 4:
	The paradigm was originally invented for parallel computers in the 1980s, especially computers built with [[transputer]] microprocessors by [[INMOS]], or similar architectures. [[Occam programming language\|Occam]] was an early process-oriented language developed for the Transputer.		The paradigm was originally invented for parallel computers in the 1980s, especially computers built with [[transputer]] microprocessors by [[INMOS]], or similar architectures. [[Occam programming language\|Occam]] was an early process-oriented language developed for the Transputer.

	Some derivations have evolved from the [[message passing]] paradigm of Occam to enable uniform efficiency when porting applications between [[distributed memory]] and shared memory parallel computers {{Citation needed\|date=June 2012}}. The first such derived example appears in the programming language [[Ease programming language\|Ease]] designed at Yale University<ref name="process">{{cite paper \| last=Ericsson-Zenith \| title=Programming with Ease; Semiotic definition of the language\|publisher=Yale University, Computer Science Technical Report YALEU/DCS/RR-809\|year=1990}}</ref><ref name="process2">{{cite book \| last=Ericsson-Zenith \|title=Process Interaction Models\|publisher=Paris University\|year=1992}}</ref> in 1990. Similar models have appeared since in the loose combination of SQL databases and objected oriented languages such as [[Java (programming language)\|Java]], often referred to as object-relational models and widely used in large scale distributed systems today. The paradigm is likely to appear on desktop computers as microprocessors increase the number of processors ([[Multi-core processor\|multicore]]) per chip.		Some derivations have evolved from the [[message passing]] paradigm of Occam to enable uniform efficiency when porting applications between [[distributed memory]] and [[shared memory]] parallel computers {{Citation needed\|date=June 2012}}. The first such derived example appears in the programming language [[Ease programming language\|Ease]] designed at Yale University<ref name="process">{{cite paper \| last=Ericsson-Zenith \| title=Programming with Ease; Semiotic definition of the language\|publisher=Yale University, Computer Science Technical Report YALEU/DCS/RR-809\|year=1990}}</ref><ref name="process2">{{cite book \| last=Ericsson-Zenith \|title=Process Interaction Models\|publisher=Paris University\|year=1992}}</ref> in 1990. Similar models have appeared since in the loose combination of SQL databases and objected oriented languages such as [[Java (programming language)\|Java]], often referred to as object-relational models and widely used in large scale distributed systems today. The paradigm is likely to appear on desktop computers as microprocessors increase the number of processors ([[Multi-core processor\|multicore]]) per chip.

	The [[Actor model]] might usefully be described as a specialised kind of process-oriented system in which the message-passing model is restricted to the simple fixed case of one infinite input queue per process (i.e. actor), to which any other process can send messages.		The [[Actor model]] might usefully be described as a specialised kind of process-oriented system in which the message-passing model is restricted to the simple fixed case of one infinite input queue per process (i.e. actor), to which any other process can send messages.

Jarble: linking

2020-03-20T00:17:47Z

linking

← Previous revision		Revision as of 00:17, 20 March 2020
Line 4:		Line 4:
	The paradigm was originally invented for parallel computers in the 1980s, especially computers built with [[transputer]] microprocessors by [[INMOS]], or similar architectures. [[Occam programming language\|Occam]] was an early process-oriented language developed for the Transputer.		The paradigm was originally invented for parallel computers in the 1980s, especially computers built with [[transputer]] microprocessors by [[INMOS]], or similar architectures. [[Occam programming language\|Occam]] was an early process-oriented language developed for the Transputer.

	Some derivations have evolved from the [[message passing]] paradigm of Occam to enable uniform efficiency when porting applications between distributed memory and shared memory parallel computers {{Citation needed\|date=June 2012}}. The first such derived example appears in the programming language [[Ease programming language\|Ease]] designed at Yale University<ref name="process">{{cite paper \| last=Ericsson-Zenith \| title=Programming with Ease; Semiotic definition of the language\|publisher=Yale University, Computer Science Technical Report YALEU/DCS/RR-809\|year=1990}}</ref><ref name="process2">{{cite book \| last=Ericsson-Zenith \|title=Process Interaction Models\|publisher=Paris University\|year=1992}}</ref> in 1990. Similar models have appeared since in the loose combination of SQL databases and objected oriented languages such as [[Java (programming language)\|Java]], often referred to as object-relational models and widely used in large scale distributed systems today. The paradigm is likely to appear on desktop computers as microprocessors increase the number of processors ([[Multi-core processor\|multicore]]) per chip.		Some derivations have evolved from the [[message passing]] paradigm of Occam to enable uniform efficiency when porting applications between [[distributed memory]] and shared memory parallel computers {{Citation needed\|date=June 2012}}. The first such derived example appears in the programming language [[Ease programming language\|Ease]] designed at Yale University<ref name="process">{{cite paper \| last=Ericsson-Zenith \| title=Programming with Ease; Semiotic definition of the language\|publisher=Yale University, Computer Science Technical Report YALEU/DCS/RR-809\|year=1990}}</ref><ref name="process2">{{cite book \| last=Ericsson-Zenith \|title=Process Interaction Models\|publisher=Paris University\|year=1992}}</ref> in 1990. Similar models have appeared since in the loose combination of SQL databases and objected oriented languages such as [[Java (programming language)\|Java]], often referred to as object-relational models and widely used in large scale distributed systems today. The paradigm is likely to appear on desktop computers as microprocessors increase the number of processors ([[Multi-core processor\|multicore]]) per chip.

	The [[Actor model]] might usefully be described as a specialised kind of process-oriented system in which the message-passing model is restricted to the simple fixed case of one infinite input queue per process (i.e. actor), to which any other process can send messages.		The [[Actor model]] might usefully be described as a specialised kind of process-oriented system in which the message-passing model is restricted to the simple fixed case of one infinite input queue per process (i.e. actor), to which any other process can send messages.

MinutiaeAnalysis: /* External links */ Replaced dead link to student website with link to thesis by same student. Deleted other external as dead, not in internet archive.

2016-12-30T05:45:00Z

External links: Replaced dead link to student website with link to thesis by same student. Deleted other external as dead, not in internet archive.

← Previous revision		Revision as of 05:45, 30 December 2016
Line 20:		Line 20:

	==External links==		==External links==
			* [http://digitalscholarship.unlv.edu/cgi/viewcontent.cgi?article=2392&context=thesesdissertations Sowders, Matthew, "ProcessJ: A process-oriented programming language" (2011). UNLV Theses, Dissertations, Professional Papers, and Capstones. Paper 1393.]
	* [http://webdigg.net/Process/Process-Interaction-Models/ Process Interaction Models]
	* [http://www.cs.unlv.edu/~matt/research/Joccam-content.html A new process oriented language with Java-like syntax targeting multiple execution architectures] {{dead link\|date=June 2012}}

	[[Category:Programming paradigms]]		[[Category:Programming paradigms]]

RickBeton at 22:24, 2 August 2016

2016-08-02T22:24:13Z

← Previous revision		Revision as of 22:24, 2 August 2016
Line 6:		Line 6:
	Some derivations have evolved from the [[message passing]] paradigm of Occam to enable uniform efficiency when porting applications between distributed memory and shared memory parallel computers {{Citation needed\|date=June 2012}}. The first such derived example appears in the programming language [[Ease programming language\|Ease]] designed at Yale University<ref name="process">{{cite paper \| last=Ericsson-Zenith \| title=Programming with Ease; Semiotic definition of the language\|publisher=Yale University, Computer Science Technical Report YALEU/DCS/RR-809\|year=1990}}</ref><ref name="process2">{{cite book \| last=Ericsson-Zenith \|title=Process Interaction Models\|publisher=Paris University\|year=1992}}</ref> in 1990. Similar models have appeared since in the loose combination of SQL databases and objected oriented languages such as [[Java (programming language)\|Java]], often referred to as object-relational models and widely used in large scale distributed systems today. The paradigm is likely to appear on desktop computers as microprocessors increase the number of processors ([[Multi-core processor\|multicore]]) per chip.		Some derivations have evolved from the [[message passing]] paradigm of Occam to enable uniform efficiency when porting applications between distributed memory and shared memory parallel computers {{Citation needed\|date=June 2012}}. The first such derived example appears in the programming language [[Ease programming language\|Ease]] designed at Yale University<ref name="process">{{cite paper \| last=Ericsson-Zenith \| title=Programming with Ease; Semiotic definition of the language\|publisher=Yale University, Computer Science Technical Report YALEU/DCS/RR-809\|year=1990}}</ref><ref name="process2">{{cite book \| last=Ericsson-Zenith \|title=Process Interaction Models\|publisher=Paris University\|year=1992}}</ref> in 1990. Similar models have appeared since in the loose combination of SQL databases and objected oriented languages such as [[Java (programming language)\|Java]], often referred to as object-relational models and widely used in large scale distributed systems today. The paradigm is likely to appear on desktop computers as microprocessors increase the number of processors ([[Multi-core processor\|multicore]]) per chip.

	The [[Actor model]] might usefully be described as a specialised kind of process-oriented ~~model~~ in which the message-passing model is restricted to the simple fixed case of one infinite input queue per process (i.e. actor), to which any other process can send messages.		The [[Actor model]] might usefully be described as a specialised kind of process-oriented system in which the message-passing model is restricted to the simple fixed case of one infinite input queue per process (i.e. actor), to which any other process can send messages.

	==See also==		==See also==

RickBeton: Para added on relationship to the actor model

2016-08-02T22:23:21Z

Para added on relationship to the actor model

← Previous revision		Revision as of 22:23, 2 August 2016
Line 5:		Line 5:

	Some derivations have evolved from the [[message passing]] paradigm of Occam to enable uniform efficiency when porting applications between distributed memory and shared memory parallel computers {{Citation needed\|date=June 2012}}. The first such derived example appears in the programming language [[Ease programming language\|Ease]] designed at Yale University<ref name="process">{{cite paper \| last=Ericsson-Zenith \| title=Programming with Ease; Semiotic definition of the language\|publisher=Yale University, Computer Science Technical Report YALEU/DCS/RR-809\|year=1990}}</ref><ref name="process2">{{cite book \| last=Ericsson-Zenith \|title=Process Interaction Models\|publisher=Paris University\|year=1992}}</ref> in 1990. Similar models have appeared since in the loose combination of SQL databases and objected oriented languages such as [[Java (programming language)\|Java]], often referred to as object-relational models and widely used in large scale distributed systems today. The paradigm is likely to appear on desktop computers as microprocessors increase the number of processors ([[Multi-core processor\|multicore]]) per chip.		Some derivations have evolved from the [[message passing]] paradigm of Occam to enable uniform efficiency when porting applications between distributed memory and shared memory parallel computers {{Citation needed\|date=June 2012}}. The first such derived example appears in the programming language [[Ease programming language\|Ease]] designed at Yale University<ref name="process">{{cite paper \| last=Ericsson-Zenith \| title=Programming with Ease; Semiotic definition of the language\|publisher=Yale University, Computer Science Technical Report YALEU/DCS/RR-809\|year=1990}}</ref><ref name="process2">{{cite book \| last=Ericsson-Zenith \|title=Process Interaction Models\|publisher=Paris University\|year=1992}}</ref> in 1990. Similar models have appeared since in the loose combination of SQL databases and objected oriented languages such as [[Java (programming language)\|Java]], often referred to as object-relational models and widely used in large scale distributed systems today. The paradigm is likely to appear on desktop computers as microprocessors increase the number of processors ([[Multi-core processor\|multicore]]) per chip.

			The [[Actor model]] might usefully be described as a specialised kind of process-oriented model in which the message-passing model is restricted to the simple fixed case of one infinite input queue per process (i.e. actor), to which any other process can send messages.

	==See also==		==See also==

RickBeton at 22:19, 2 August 2016

2016-08-02T22:19:11Z

← Previous revision		Revision as of 22:19, 2 August 2016
Line 2:		Line 2:
	'''Process-oriented programming''' is a [[programming paradigm]] that separates the concerns of data structures and the concurrent processes that act upon them. The data structures in this case are typically persistent, complex, and large scale - the subject of general purpose applications, as opposed to specialized processing of specialized data sets seen in high productivity applications (HPC). The model allows the creation of large scale applications that partially share common data sets. Programs are functionally decomposed into parallel processes that create and act upon logically shared data.		'''Process-oriented programming''' is a [[programming paradigm]] that separates the concerns of data structures and the concurrent processes that act upon them. The data structures in this case are typically persistent, complex, and large scale - the subject of general purpose applications, as opposed to specialized processing of specialized data sets seen in high productivity applications (HPC). The model allows the creation of large scale applications that partially share common data sets. Programs are functionally decomposed into parallel processes that create and act upon logically shared data.

	The paradigm was originally invented for parallel computers in the 1980s, especially computers built with [[transputer]] microprocessors by [[INMOS]], or similar architectures. [[Occam programming language\|Occam]] was an early process-oriented language developed for the Transputer. Some derivations have evolved from the [[message passing]] paradigm of Occam to enable uniform efficiency when porting applications between distributed memory and shared memory parallel computers {{Citation needed\|date=June 2012}}.		The paradigm was originally invented for parallel computers in the 1980s, especially computers built with [[transputer]] microprocessors by [[INMOS]], or similar architectures. [[Occam programming language\|Occam]] was an early process-oriented language developed for the Transputer.

	The first such derived example appears in the programming language [[Ease programming language\|Ease]] designed at Yale University<ref name="process">{{cite paper \| last=Ericsson-Zenith \| title=Programming with Ease; Semiotic definition of the language\|publisher=Yale University, Computer Science Technical Report YALEU/DCS/RR-809\|year=1990}}</ref><ref name="process2">{{cite book \| last=Ericsson-Zenith \|title=Process Interaction Models\|publisher=Paris University\|year=1992}}</ref> in 1990. Similar models have appeared since in the loose combination of SQL databases and objected oriented languages such as [[Java (programming language)\|Java]], often referred to as object-relational models and widely used in large scale distributed systems today. The paradigm is likely to appear on desktop computers as microprocessors increase the number of processors ([[Multi-core processor\|multicore]]) per chip.		Some derivations have evolved from the [[message passing]] paradigm of Occam to enable uniform efficiency when porting applications between distributed memory and shared memory parallel computers {{Citation needed\|date=June 2012}}. The first such derived example appears in the programming language [[Ease programming language\|Ease]] designed at Yale University<ref name="process">{{cite paper \| last=Ericsson-Zenith \| title=Programming with Ease; Semiotic definition of the language\|publisher=Yale University, Computer Science Technical Report YALEU/DCS/RR-809\|year=1990}}</ref><ref name="process2">{{cite book \| last=Ericsson-Zenith \|title=Process Interaction Models\|publisher=Paris University\|year=1992}}</ref> in 1990. Similar models have appeared since in the loose combination of SQL databases and objected oriented languages such as [[Java (programming language)\|Java]], often referred to as object-relational models and widely used in large scale distributed systems today. The paradigm is likely to appear on desktop computers as microprocessors increase the number of processors ([[Multi-core processor\|multicore]]) per chip.

	==See also==		==See also==

RickBeton: Rebalanced the description of Occam here, which is an example of a process-oriented language and had been mis-described

2016-08-02T22:17:17Z

Rebalanced the description of Occam here, which is an example of a process-oriented language and had been mis-described

← Previous revision		Revision as of 22:17, 2 August 2016
Line 2:		Line 2:
	'''Process-oriented programming''' is a [[programming paradigm]] that separates the concerns of data structures and the concurrent processes that act upon them. The data structures in this case are typically persistent, complex, and large scale - the subject of general purpose applications, as opposed to specialized processing of specialized data sets seen in high productivity applications (HPC). The model allows the creation of large scale applications that partially share common data sets. Programs are functionally decomposed into parallel processes that create and act upon logically shared data.		'''Process-oriented programming''' is a [[programming paradigm]] that separates the concerns of data structures and the concurrent processes that act upon them. The data structures in this case are typically persistent, complex, and large scale - the subject of general purpose applications, as opposed to specialized processing of specialized data sets seen in high productivity applications (HPC). The model allows the creation of large scale applications that partially share common data sets. Programs are functionally decomposed into parallel processes that create and act upon logically shared data.

	The paradigm was originally invented for parallel computers in the 1980s, especially computers built with [[transputer]] microprocessors by [[INMOS]], or similar architectures. It ~~evolved~~ to ~~meet~~ ~~deficiencies~~ in the [[message passing]] paradigm of [[Occam ~~programming language\|Occam]] {{Citation needed\|date=June 2012}} and~~ enable uniform efficiency when porting applications between distributed memory and shared memory parallel computers.		The paradigm was originally invented for parallel computers in the 1980s, especially computers built with [[transputer]] microprocessors by [[INMOS]], or similar architectures. [[Occam programming language\|Occam]] was an early process-oriented language developed for the Transputer. Some derivations have evolved from the [[message passing]] paradigm of Occam to enable uniform efficiency when porting applications between distributed memory and shared memory parallel computers {{Citation needed\|date=June 2012}}.

	The first ~~example~~ of ~~the paradigm~~ appears in the programming language [[Ease programming language\|Ease]] designed at Yale University<ref name="process">{{cite paper \| last=Ericsson-Zenith \| title=Programming with Ease; Semiotic definition of the language\|publisher=Yale University, Computer Science Technical Report YALEU/DCS/RR-809\|year=1990}}</ref><ref name="process2">{{cite book \| last=Ericsson-Zenith \|title=Process Interaction Models\|publisher=Paris University\|year=1992}}</ref> in 1990. Similar models have appeared since in the loose combination of SQL databases and objected oriented languages such as [[Java (programming language)\|Java]], often referred to as object-relational models and widely used in large scale distributed systems today. The paradigm is likely to appear on desktop computers as microprocessors increase the number of processors ([[Multi-core processor\|multicore]]) per chip.		The first such derived example appears in the programming language [[Ease programming language\|Ease]] designed at Yale University<ref name="process">{{cite paper \| last=Ericsson-Zenith \| title=Programming with Ease; Semiotic definition of the language\|publisher=Yale University, Computer Science Technical Report YALEU/DCS/RR-809\|year=1990}}</ref><ref name="process2">{{cite book \| last=Ericsson-Zenith \|title=Process Interaction Models\|publisher=Paris University\|year=1992}}</ref> in 1990. Similar models have appeared since in the loose combination of SQL databases and objected oriented languages such as [[Java (programming language)\|Java]], often referred to as object-relational models and widely used in large scale distributed systems today. The paradigm is likely to appear on desktop computers as microprocessors increase the number of processors ([[Multi-core processor\|multicore]]) per chip.

	==See also==		==See also==

			*[[Communicating process architectures]]
	*[[Massively parallel processing]]		*[[Massively parallel processing]]
	*[[Parallel computing]]		*[[Parallel computing]]