2002
DOI: 10.1007/3-540-38093-0_12
|View full text |Cite
|
Sign up to set email alerts
|

Message Queuing Patterns for Middleware-Mediated Transactions

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
5
0

Year Published

2004
2004
2015
2015

Publication Types

Select...
2
2
1

Relationship

0
5

Authors

Journals

citations
Cited by 5 publications
(5 citation statements)
references
References 6 publications
0
5
0
Order By: Relevance
“…The other possible building blocks are SOAP client pattern, message queue pattern [15], etc. Also building blocks can be extracted from industrial experience and synthesized in academic settings [20], [23], [22], [19].…”
Section: Related Workmentioning
confidence: 99%
“…The other possible building blocks are SOAP client pattern, message queue pattern [15], etc. Also building blocks can be extracted from industrial experience and synthesized in academic settings [20], [23], [22], [19].…”
Section: Related Workmentioning
confidence: 99%
“…Furthermore, CSN also provides a conceptual model for sensor data delivery: how sensors send data out and applications retrieves data. The conceptual data delivery model is based on the Publish/Subscribe Model (e.g., JMS Messaging Model) [15]. The Publish/Subscribe Model is based on three concepts.…”
Section: Conceptual Designmentioning
confidence: 99%
“…Furthermore, CSN also provides a conceptual model for sensor data delivery: how sensors send data out and applications retrieves data. The conceptual data delivery model is based on the Publish/Subscribe Model (e.g., JMS Messaging Model) [15] Figure 2 illustrates how the CSN data delivery model based on message queues works. In this example, there are four sensors (singleton sensor networks) and two sensor networks with those sensors as network members.…”
Section: Sensor Data Delivery Modelmentioning
confidence: 99%
See 1 more Smart Citation
“…To summarize the roles of each party in a message transaction, the message producer has a contract with the message server; the message server has a contract with the message consumer. Further information on integrating messaging with transactions is available in [11,12] and Chapter ?? (Transaction Middleware).…”
Section: Producermentioning
confidence: 99%