Cart
[Home] [By Thread] [By Date] [Recent Entries]
Ok. That was actually how I thought things worked originally until we got into this thread. I might still need the registry for further processes of discovery, but not necessarily for drilling into one I've identified as a candidate. Now, you posted this excellent set of points. If we concentrate on this list, I may achieve REST satori. "REST is defined by four interface constraints: 1. identification of resources; 2. manipulation of resources through representations;* 3. self-descriptive messages; 4. hypermedia as the engine of application state." Please help me understand how each of these are defined in your use of the web technologies vs what the web service API method advocates define. Number four may be the loosest definition. It is hard to spec "hypermedia" as "engine". len -----Original Message----- From: Paul Prescod [mailto:paul@p...] Once you've got the URI for their service description (WSDL, IDL, RDF or whatever) on their site, you don't need to use the registry anymore. All you need is to follow a hyperlink from the registry to their machine processable documentation, at their site.
|
