UPDATE Warning, this answer is extremely out of date now that OData V4 is available. I wrote a post on the subject a while ago here. As Franci said, OData is based on Atom Pub. However, they have layered some functionality on top and unfortunately have ignored some of the REST constraints in the process. … Read more
WSDL (Web Services Description Language) describes your service and its operations – what is the service called, which methods does it offer, what kind of in parameters and return values do these methods have? It’s a description of the behavior of the service – it’s functionality. XSD (Xml Schema Definition) describes the static structure of … Read more
An API (Application Programming Interface) is the means by which third parties can write code that interfaces with other code. A Web Service is a type of API, one that almost always operates over HTTP (though some, like SOAP, can use alternate transports, like SMTP). The official W3C definition mentions that Web Services don’t necessarily … Read more
It’s 99th percentile. It means that 99% of the requests should be faster than given latency. In other words only 1% of the requests are allowed to be slower.
404 is just the HTTP response code. On top of that, you can provide a response body and/or other headers with a more meaningful error message that developers will see.
When you use a web service you have a client and a server: If the server fails the client must take responsibility to handle the error. When the server is working again the client is responsible of resending it. If the server gives a response to the call and the client fails the operation is … Read more
I agree with Greg that a two phase approach is a reasonable solution, however I would do it the other way around. I would do: POST http://server/data/media body: { “Name”: “Test”, “Latitude”: 12.59817, “Longitude”: 52.12873 } To create the metadata entry and return a response like: 201 Created Location: http://server/data/media/21323 { “Name”: “Test”, “Latitude”: 12.59817, … Read more
This is a shorter and hopefully clearer answer… Yes, the endpoint is the URL where your service can be accessed by a client application. The same web service can have multiple endpoints, for example in order to make it available using different protocols.
The limit is dependent on both the server and the client used (and if applicable, also the proxy the server or the client is using). Most web servers have a limit of 8192 bytes (8 KB), which is usually configurable somewhere in the server configuration. As to the client side matter, the HTTP 1.1 specification even … Read more
I noticed this question a couple of days late, but I feel that I can add some insight. I hope this can be helpful towards your RESTful venture. Point 1: Am I understanding it right? You understood right. That is a correct representation of a RESTful architecture. You may find the following matrix from Wikipedia … Read more