I feel that other answers, while correct, don’t quite explain the root of the question: REST is a subset of HTTP. This means everything that can be done via REST can be done via HTTP but not everything that can be done via HTTP can be done via REST. That is why $resource uses $http … Read more
You mentioned using json2.js to stringify your data, but the POSTed data appears to be URLEncoded JSON You may have already seen it, but this post about the invalid JSON primitive covers why the JSON is being URLEncoded. I’d advise against passing a raw, manually-serialized JSON string into your method. ASP.NET is going to automatically … Read more
I’m surprised nobody has mentioned the new Fetch API, supported by all browsers except IE11 at the time of writing. It simplifies the XMLHttpRequest syntax you see in many of the other examples. The API includes a lot more, but start with the fetch() method. It takes two arguments: A URL or an object representing … 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
Found a solution on this website All you need is to add the following to your web.config <configuration> <system.web> <webServices> <protocols> <add name=”HttpGet”/> <add name=”HttpPost”/> </protocols> </webServices> </system.web> </configuration> More info from Microsoft
Use the static method Guid.NewGuid() instead of calling the default constructor. var responseObject = proxy.CallService(new RequestObject { Data = “misc. data”, Guid = Guid.NewGuid() });
These are different Form content types defined by W3C. If you want to send simple text/ ASCII data, then x-www-form-urlencoded will work. This is the default. But if you have to send non-ASCII text or large binary data, the form-data is for that. You can use Raw if you want to send plain text or … Read more