Skip to main content
  • 2356 Accesses

Abstract

This chapter explores what a service following the REST architectural style should look like to a caller. Considering that such an API is supposed to better leverage the HTTP protocol and its various aspects, focusing on HTTP verbs and resources, its interface will be markedly different from your typical RPC-style API. So, as we design the service, we will compare the REST approach with a more traditional RPC or SOAP approach.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 54.99
Price excludes VAT (USA)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 69.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Notes

  1. 1.

    http://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypertext-driven

Author information

Authors and Affiliations

Authors

Rights and permissions

Reprints and permissions

Copyright information

© 2014 Jamie Kurtz

About this chapter

Cite this chapter

Kurtz, J., Wortman, B. (2014). What Is RESTful?. In: ASP.NET Web API 2: Building a REST Service from Start to Finish. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4842-0109-1_2

Download citation

Publish with us

Policies and ethics