Proceedings International Symposium on Software Engineering for Parallel and Distributed Systems PDSE-99 2000
DOI: 10.1109/pdse.2000.847853
|View full text |Cite
|
Sign up to set email alerts
|

Filtering and scalability in the ECO distributed event model

Abstract: Abstract

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
22
0

Year Published

2002
2002
2013
2013

Publication Types

Select...
6
1
1

Relationship

0
8

Authors

Journals

citations
Cited by 20 publications
(22 citation statements)
references
References 5 publications
0
22
0
Order By: Relevance
“…Examples include ECO [21], JavaPS [13], EventJava [14], Ptolemy [38], and EScala [19]. None of these provide any other features than propagation of implicit invocations; focusing on centralized deployments, Ptolemy or EScala could easily provide information on the number of publishers per subscriber or vice-versa.…”
Section: Implicit Invocationsmentioning
confidence: 99%
“…Examples include ECO [21], JavaPS [13], EventJava [14], Ptolemy [38], and EScala [19]. None of these provide any other features than propagation of implicit invocations; focusing on centralized deployments, Ptolemy or EScala could easily provide information on the number of publishers per subscriber or vice-versa.…”
Section: Implicit Invocationsmentioning
confidence: 99%
“…Simple predicated event handlers 1, 1, 1 . This includes content-based publish/subscribe multicast systems such as Siena [9] or languages inspired by the model (e.g., ECO [10], Java P S [11]), as well as Actor-based languages or Actor libraries supporting predicates on individual messages (e.g., Erlang 2 , Scala Actors [4], AmbientTalk [12]). Join languages 1, #, 0 .…”
Section: State Of the Art Of Cedmentioning
confidence: 99%
“…There are three main types of distribute event-based systems [15]: co-located middleware -the event service is in the same address space as the clients (e.g., mSECO [11]); single separated middleware -the event service is located on a single machine while the clients are distributed on other machines (e.g., CORBA); multiple separated middleware -clients and event service are distributed and execute on different machines or address spaces (e.g., SIENA). While our approach could be applied to all three types of system, we chose SIENA because both the clients and middleware are distributed making it a challenging architecture in which to discover mismatch.…”
Section: Distributed Event-based Systemsmentioning
confidence: 99%