I was reading the comparison between SOAP and XML-RPC from the following article.
http://weblog.masukomi.org/writings/xml-rpc_vs_soap.htm
In the article it is mentioned that SOAP can:
1).Can specify recipient
2).Require client understanding
3).Message specific processing instructions
Can some one please explain the above mentioned points with example?.
I hope this helps.
http://r4r.co.in/webservice/01/tutorial/basic/soap.shtml
Related
Whenever I have to create a RESTful web service and the use case implies on getting data based on a set of search criteria, I always opted for a POST request with the parameters in the body instead of a GET request for all the obvious reasons. I've seen it a dozen of times so I figured is was best practice.
Most recently I stumbled upon this interesting blog article by Evert Pot where he comments on the downsides of the POST verb and simply notes on using the REPORT verb instead. He also states that "its semantics are well defined and it works everywhere".
After reading the post I've been trying to find some more information on this REPORT verb but not much can be found. I know it was part of RFC-3253 as a way to obtain information about a resource but other than that I am clueless.
My question are the following:
Is REPORT really a better alternative than POST in the case of requesting a resource based on a set of search criteria?
Is it wise to start using it or is it too risky? I'm seeing lots of
HTTP Method REPORT not supported issues from various tools and frameworks.
Why does it seem like it is neglected over the years and why do we
know so little about it?
What could other valid use-cases be for using this verb?
Thank you in advance.
The REPORT method is defined in the webdav scope, including the Depth header field, and the DAV:version-tree report request.
Using it outside webdav you may incur in some unspecified behavior.
A REPORT request is an extensible mechanism for obtaining information
about a resource.
This is semantically different from a POST request, where you usually transfer the
expected representation you want to convey to the server.
Consider that in the HTTP method registry REPORT is marked as "safe" and "idempotent", while that's not the case for POST
the value of a report can depend on additional information
specified in the REPORT request body and in the REPORT request
headers.
Those are tied to webdav. To foster REPORT usage we should extend its definition and disentangle it from webdav.
Is that possible? I know I can extract some timing data using the Navigation Timing API, but that's not enough. Also know that I can use a proxy like Browsermob Proxy, but I was wondering if I could do the same with just client side code (JS).
Perhaps something using the Resource Timing API might be what you are looking for? I am looking for an answer to a similar issue and I found this article which has been useful:
http://calendar.perfplanet.com/2012/an-introduction-to-the-resource-timing-api/
You can see the code that implements the API here:
https://github.com/andydavies/waterfall/blob/master/waterfall.js
I hope this is helpful.
I want to better my understanding behind the mechanisms of the Http protocol from a web application dev's perspective. I want to clear my confusion about what objects are involved such as the session object and the request object and when are they generated and terminated and what attributes of them we would commonly use during a web application. At the expense of not making much sense.. I won't say too much more. I just wish to be pointed to a good source of knowledge on this whether it be a book/video/web page/or a detailed response to this post. Thanks kindly.
Try this for HTTP and REST.
Here's a good place to start for sessions.
Wikipedia is a really good source for all HTTP topics as well.
I have a SoapUI Mock Service. I would like it to use WS-Security.
I configured the project WS-Security Configurations, both Outgoing and Incoming.
I use a Test Suite to send a request and it is properly processed with Timestamp, Signature and Encrypt WSS Entries. But the response from the Mock Service is a plain text fault:
Missing operation for soapAction [] and body element
[{http://www.w3.org/2001/04/xmlenc#}EncryptedData] with SOAP Version [SOAP 1.1]
From this message I guess that the mock service did not recognize encryption HTML elements. Am I right?
Is there a way to encrypt SoapUI mock service responses using WS-Security?
It is possible. The options can be found after clicking on the mock service in the bottom left part of the screen (unlike all other configuration options that are available in popups). There you can choose outgoing and incoming security configuration set from a dropdown.
It is hidden so well that I ran into the problem twice within three months, performed a research and found my own unanswered question in StackOverflow before a friend showed me the solution.
So I post the answer should anyone need that.
I wanted to know if JSON is still used in live applications? I am creating a service and want to understand if I should output data using JSON too?
What is the latest standard now?
JSON is very popular, and there is no sign that this is changing.
I am creating a service and want to understand if I should output data using JSON too?
You really need to ask the potential customers of the service that question. Or at least, give us some hint as to what the service is and what clients are likely to use it.
What is the latest standard now?
There is no official standard for JSON. In theory, JSON is a subset of ECMAScript (aka JavaScript), so the relevant ECMAScript standard would be normative.
In practice, JSON is implemented in many languages independently of ECMAScript. The description on the JSON.org website, and IETF RFC 4627 are probably the most relevant to someone implementing JSON for themselves, but neither of these sources have the authority of a standard. If you want JSON libraries, the JSON.org site is a good place to start looking.
Yes, JSON is still very popular. Even Google web services API gives search output in JSON.
Take a look at this example:
http://zamples.com/JspExplorer/samples/google.jsp
Overwhelmingly yes. For me, JSON is the transport format of choice for AJAX requests and inter-application data sharing. To date, there are 1271 questions about JSON on SO.