ArRESTed development: Guidelines for designing REST frameworks

IEEE Internet Computing

Volumn 16, Issue 4, 2012, Pages 26-35

  Zuzak, Ivan ^a   Schreier, Silvia ^b  

^a UNIVERSITY OF ZAGREB   (Croatia)

^b UNIVERSITY OF HAGEN   (Germany)

Author keywords

Computer architecture; Engines; frameworks; Guidelines; hypermedia; Internet; Media; Protocols; REST; Servers; Web

Indexed keywords

FRAMEWORKS; GUIDELINES; HYPERMEDIA; MEDIA; REST; WEB;

COMPUTER ARCHITECTURE; COMPUTER SYSTEMS; ENGINES; INTERNET; NETWORK PROTOCOLS; SERVERS;

INTERNET PROTOCOLS;

EID: 84864925543     PISSN: 10897801     EISSN: None     Source Type: Journal    
DOI: 10.1109/MIC.2012.60     Document Type: Article

References (7)

1. R.T. Fielding, Architectural Styles and the Design of Network-based Software Architectures, doctoral dissertation, Univ. of California, Irvine, 2000.
2. C. Pautasso, O. Zimmermann, and F. Leymann, "RESTful Web Services vs. 'Big' Web Services: Making the Right Architectural Decision," Proc. 17th Int'l. Conf. World Wide Web, ACM, 2008, pp. 805-814.
3. S. Vinoski, "RPC and REST: Dilemma, Disruption, and Displacement," IEEE Internet Computing, vol. 12, no. 5, 2008, pp. 92-95.
4. M. Broy, "Can Practitioners Neglect Theory and Theoreticians Neglect Practice?" Computer, vol. 44, no. 10, 2011, pp. 19-24.
5. I. Zuzak, I. Budiselic, and G. Delac, "Formal Modeling of RESTful Systems Using Finite-State Machines," Web Engineering, LNCS 6757, Springer, 2011, pp. 346-360.
6. S. Schreier, "Modeling RESTful Applications," Proc. 2nd Int'l Workshop RESTful Design, ACM, 2011, pp. 15-21.
7. R.T. Fielding, "REST APIs Must Be Hypertext-Driven," blog, 20 Oct. 200s8; http://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypertext- driven.