Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page

Jan Stroet

dblp:30/659 · DBLP profile ↗
← Back
1ranked-venue papers
0as first author
0since 2021 · last 1981
—ORCID · none

Domains — the database's venue-derived domains; a paper can count in several

Software engineering, systems software and programming languages · 1

Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.

Software engineering, system software, and programming languages
1 paper
Operating systems · 77% Concurrent programming · 23%

Topics — the 2 heaviest of 2, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Operating systems
interprocess communication
0.011981
Process Communication Based on Input Specifications · ACM Trans. Program. Lang. Syst. 1981
Concurrent programming › synchronization
process synchronization
0.011981
Process Communication Based on Input Specifications · ACM Trans. Program. Lang. Syst. 1981

Methods — techniques the papers use, named apart from their topics

production rules · 0.0message passing · 0.0
YearPublicationVenuePosition
1981 Process Communication Based on Input Specifications
abstract
InputInput tools, originally introduced as a language model for interactive systems and based on high-level, input-driven objects, have been developed into a model for communicating parallel processes, called the input tool process model (ITP).In this model every process contains an input rule, comparable to the right-hand side of a production rule.This rule specifies in an expression the patterns and sources of input it exPects and where the input is to be handled.The reception of the input triggers action inside the too! process.As part of the action, messages may be sent to other processes, with destination specified to a varying degree of identification.A potential candidate for a message is any tool process with the correct type of message slot.Because sending tool processes do not have to specify completely the identity of receiving tool processes, and vice versa, ITP provides a fully dynamic communication model.Most communication aspects of other recently developed models are contained in this model.Synchronization of processes is accomplished implicitly by the input specification; explicit synchro-nizatiQn constructs such as monitors and guarded regions can therefore be easily simulated.The ITP constructs provide a general concept for interprocess communication.Its application areas range from interaction via process control to operating systems.From a programming point of view, the language constructs offered are not in any way dependent on whether processes run on single or multiple processors.
Jan van den Bos, Marinus J. Plasmeijer, Jan Stroet
ACM Trans. Program. Lang. Syst.3