2005
DOI: 10.1007/11580850_12
|View full text |Cite
|
Sign up to set email alerts
|

Concurrency Among Strangers

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
4
1

Citation Types

0
17
0

Year Published

2006
2006
2013
2013

Publication Types

Select...
4
3
2

Relationship

0
9

Authors

Journals

citations
Cited by 68 publications
(19 citation statements)
references
References 25 publications
0
17
0
Order By: Relevance
“…Although shared-memory implementations are often possible, the burden of preventing unwanted thread interleavings without crippling performance is onerous. Many have instead adopted asynchronous programming models in which processes communicate by posting messages/tasks to others' message/task queues- [19] discuss why such models provide good programming abstractions. Single-process systems such as the JavaScript page-loading engine of modern web browsers [1], and the highly-scalable Node.js asynchronous web server [11], execute a series of short-lived tasks one-by-one, each task potentially queueing additional tasks to be executed later.…”
Section: Introductionmentioning
confidence: 99%
“…Although shared-memory implementations are often possible, the burden of preventing unwanted thread interleavings without crippling performance is onerous. Many have instead adopted asynchronous programming models in which processes communicate by posting messages/tasks to others' message/task queues- [19] discuss why such models provide good programming abstractions. Single-process systems such as the JavaScript page-loading engine of modern web browsers [1], and the highly-scalable Node.js asynchronous web server [11], execute a series of short-lived tasks one-by-one, each task potentially queueing additional tasks to be executed later.…”
Section: Introductionmentioning
confidence: 99%
“…In these scenarios it often makes a difference whether a reference points to an object at the current location, i.e., the location of the current executing object (in the following called a near reference), or to an object at a different location (a far reference). For example, in the E programming language [4], a far reference can only be used for asynchronous method calls (named eventual sends in E), but not for synchronous method calls. In Java Remote Method Invocation (RMI) [8] accessing a remote reference may throw a RemoteException, where accessing a normal reference cannot throw such an exception.…”
Section: Introductionmentioning
confidence: 99%
“…This versatile notion of locality is not only useful for distributed programming, but also for programs running on a single computer. For example, in object-oriented languages with concurrency models based on communicating groups of objects such as E [4], AmbientTalk/2 [5], JCoBox [6], or ABS [7], the location of an object can be considered as the group it belongs to. In these scenarios it often makes a difference whether a reference points to an object at the current location, i.e., the location of the current executing object (in the following called a near reference), or to an object at a different location (a far reference).…”
Section: Introductionmentioning
confidence: 99%
“…Although sharedmemory implementations are often possible, the burden of preventing unwanted thread interleavings without crippling performance is onerous. Many have instead adopted asynchronous programming models in which processes communicate by posting messages/tasks to others' message/task queues-Miller et al [18] discuss why such models provide good programming abstractions. Single-process systems such as the JavaScript page-loading engine of modern web browsers [1], and the highly-scalable Node.js asynchronous web server [10], execute a series of short-lived tasks one-by-one, each task potentially queueing additional tasks to be executed later.…”
Section: Introductionmentioning
confidence: 99%