2009 IEEE International Conference on Web Services 2009
DOI: 10.1109/icws.2009.99
|View full text |Cite
|
Sign up to set email alerts
|

Abstract: With REST

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
31
0

Year Published

2009
2009
2017
2017

Publication Types

Select...
4
2

Relationship

3
3

Authors

Journals

citations
Cited by 22 publications
(31 citation statements)
references
References 10 publications
0
31
0
Order By: Relevance
“…Further pushing the envelope of how to apply RESTful principles to more advanced scenarios are ongoing research efforts towards support for RESTful transactions [10]. The approach presented in this paper is another contribution to this field, investigating how a REST design pattern (queries on URI-based resources, in this case feeds) can be used as a blueprint for a variety of query-oriented services on the Web.…”
Section: Discussionmentioning
confidence: 99%
See 1 more Smart Citation
“…Further pushing the envelope of how to apply RESTful principles to more advanced scenarios are ongoing research efforts towards support for RESTful transactions [10]. The approach presented in this paper is another contribution to this field, investigating how a REST design pattern (queries on URI-based resources, in this case feeds) can be used as a blueprint for a variety of query-oriented services on the Web.…”
Section: Discussionmentioning
confidence: 99%
“…Next steps for this research are the capability to create new databases and edit the schema of a database, again based on the feed metamodel. Also, the RESTful database framework can become an excellent testbed for the so-far theoretical work on RESTful Transactions [10].…”
Section: Restful Database Queriesmentioning
confidence: 99%
“…In fact, for certain models, it may be impossible to move from one state to another without performing more than one operations, for instance in the case where a student must be registered for exactly five courses, a new course cannot be added if a course is not simultaneously removed. This calls for the execution of multiple operations simultaneously over HTTP, something the authors of this paper have already made progress in specifying RESTful Transactions [17]. Even with this capability, there is a fundamental tension between processes and declarative specifications, as processes focus on the 'how' rather than the 'what' which declarative models specify.…”
Section: Implicit Process Specificationmentioning
confidence: 99%
“…Compensation mechanism can be also employed when transactions are rolled back for reasons not related to the failures of the system components (e.g., in the case of failures at the business logic level). Since the transactional approach [8] is burdened with high costs of maintenance transactions' properties, its use is not viable in applications that only require reliability.…”
Section: Related Workmentioning
confidence: 99%
“…When the rollback is finished (6), SIM requires RM U to resubmit all requests performed by the service before the failure, and not saved in the chosen recovery point (7). RM U acknowledges how many requests will be resubmitted (8). When SIM confirms that it's ready to begin the recovery process (9), all requests chosen in step (7) are sent again by the RM U (N) and re-executed by the service, in the same order as before the failure (M).…”
Section: General Idea Of Rollback-recovery Protocolmentioning
confidence: 99%