1998
DOI: 10.17487/rfc2372
|View full text |Cite
|
Sign up to set email alerts
|

Transaction Internet Protocol - Requirements and Supplemental Information

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1

Citation Types

0
3
0

Year Published

1998
1998
2006
2006

Publication Types

Select...
6
2

Relationship

1
7

Authors

Journals

citations
Cited by 14 publications
(3 citation statements)
references
References 2 publications
0
3
0
Order By: Relevance
“…Communications and component system failures on the Web are frequent. However, most W-TM approaches either do not address recovery within the Web environment [11,12,19,20], or rely on two-phase commit (2PC) based protocols to enforce ACID criteria for transaction correctness [1,5,10,3,7,6,2].…”
Section: Related Workmentioning
confidence: 99%
“…Communications and component system failures on the Web are frequent. However, most W-TM approaches either do not address recovery within the Web environment [11,12,19,20], or rely on two-phase commit (2PC) based protocols to enforce ACID criteria for transaction correctness [1,5,10,3,7,6,2].…”
Section: Related Workmentioning
confidence: 99%
“…to PULL the transaction from a remote transaction manager. It is anticipated that each TIP implementation will provide some set of APIs for this purpose ( [5] includes examples of such APIs).…”
Section: Tip Uniform Resource Locatorsmentioning
confidence: 99%
“…The focus was mainly on addressing crash recovery techniques in the two-phase commit (2PC) protocols that enforce ACID (atomic, consistent, isolated, durable) criteria. Early research on Web-db environments also concentrated on employing 2PC protocols and their recovery techniques in Web-db transactions [7,8,9,10,11,12,13,14]. However, there are problems associated with 2PC-based protocols [1].…”
Section: Related Workmentioning
confidence: 99%