2012 19th Asia-Pacific Software Engineering Conference 2012
DOI: 10.1109/apsec.2012.24
|View full text |Cite
|
Sign up to set email alerts
|

Web Platform API Design Principles and Service Contract

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1

Citation Types

0
1
0

Year Published

2014
2014
2014
2014

Publication Types

Select...
1

Relationship

0
1

Authors

Journals

citations
Cited by 1 publication
(1 citation statement)
references
References 19 publications
0
1
0
Order By: Relevance
“…If an application is communicating to the server backend, the protocol must be designed in such a way that several versions of an application will be able to talk with the current version of the server. In general, RESTful services encourage a simple model of communication that is easy to version and maintain compatibility [3]. Stateful or procedural RPCs pose more challenges because they can add more semantics to the communication that may be easier to break between versions than simple entity transfer.…”
Section: Backward Compatibilitymentioning
confidence: 99%
“…If an application is communicating to the server backend, the protocol must be designed in such a way that several versions of an application will be able to talk with the current version of the server. In general, RESTful services encourage a simple model of communication that is easy to version and maintain compatibility [3]. Stateful or procedural RPCs pose more challenges because they can add more semantics to the communication that may be easier to break between versions than simple entity transfer.…”
Section: Backward Compatibilitymentioning
confidence: 99%