Over the next few days articles introducing the Resources Over MVC (ROM) assembly will be added to the
Shoulders of Giants
- Bare Minimum Part 1 - creating a minimal read-only web service with one line of code
- Bare Minimum Part 2 - adding one more line of code to receive data (includes a sample project)
- A More Complex Sample - the start of a series of articles that will use a fuller sample to show some of the more interesting features of
the ROM assembly
- Simple Clients Part 1 - shows how the ROM assembly allows simple clients to request different representations (i.e. formats) using a querystring
- Simple Clients Part 2 - the line of code introduced in Simple Clients Part 1 also means the web service can support POST overloading via
a custom header, form variable or by using a query string parameter
- Providing Help - describes how you can provide help for client developers as part of the web serice using all the features of ASP.Net MVC
(something that is not possible in a WCF based service)
- Allowed Verbs - a key feature of the REST approach is for a web service to support discoverability as described in the phrase
"Hypermedia as the Engine of Application State". The HTTP protocol helps to take this beyond providing URIs by defining the
Allow header. With this header, a server can inform a client which verbs a resource supports (e.g. GET, POST etc.). This article shows how the ROM assembly helps you support this header.
Note: The easiest way to add the ROM assembly to your poject is to use the
More to come: Formatting the output, alternative renderers such as JSON.Net, error handling etc.