This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Demystifying RESTful Data Coupling
March/April 2008 (vol. 12 no. 2)
pp. 87-90
Steve Vinoski, Verivue
Developers who favor technologies that promote interface specialization typically raise two specific objections to the uniform-interface constraint designed into the Representational State Transfer (REST) architectural style. One is that different resources should each have specific interfaces and methods that more accurately reflect their precise functionality. The other objection to the concept of a uniform interface is that it merely shifts all coupling issues and other problems to the data exchanged between client and server. Yet, that's based on the invalid assumption that the data exchanged in a REST system is just like the data exchanged in systems such as Web services and Corba, which require interface specialization.

1. R.T. Fielding, Architectural Styles and the Design of Network-Based Software Architectures, doctoral dissertation, Dept. of Computer Science, Univ. of Calif., Irvine, 2000.
2. M. Nottingham, The Atom Syndication Format, IETF recommendation, Dec. 2005; www.ietf.org/rfcrfc4287.txt.
3. J. Gregorio and B. de hÓra, The Atom Publishing Protocol, IETF recommendation, Oct. 2007; www.ietf.org/rfcrfc5023.

Index Terms:
REST, respresentational state transfer, distributed computing, Web services, middleware, interface
Citation:
Steve Vinoski, "Demystifying RESTful Data Coupling," IEEE Internet Computing, vol. 12, no. 2, pp. 87-90, March-April 2008, doi:10.1109/MIC.2008.33
Usage of this product signifies your acceptance of the Terms of Use.