9640Re: REST API specification templates
- Sep 9, 2007--- In firstname.lastname@example.org, "A. Pagaltzis" <pagaltzis@...> wrote:
> This is a contradiction in terms. REST is defined by twoI am currently defining an interface using the REST style. What i do
> 1. Server state is exposed as a set of resources that have a
> uniform interface and are named by URIs.
> 2. The client doesnât make any assumptions about the server URI
> space; all it does is follow links.
is discover the resources and the representations of those resources.
I have a test specification, i would like to run that test and i want
Resources: TestSpec, TestRun, TestReport, TestSpecs, TestRuns,
POST http://<host/Test/TestSpecs <TestSpec>...</TestSpec>
return 201 Location: http://<host>/Test/TestSpecs/TestSpec1.xml
POST http://<host>/Test/TestRuns <TestRun
return 201 Location: http://<host>/Test/TestRuns/TestRun1.xml
In my case the client does make assumptions of where to find the
resources, but does this make the interface less RESTful?
Roger van de Kimmenade
- << Previous post in topic Next post in topic >>