Suma Rangaraj wrote:1. In one of the posts that I read, it is mentioned that the difference between REST and SOAP is that REST is stateless and SOAP is stateful.
My understanding is that the statelessness and statefulness depends on the underlying protocol. So, if we choose HTTP as a protocol then both SOAP and REST can be stateless unless we pass some session ifnormation in the request. Is my understanding correct?
2. If I am right, how do we achieve statefulness using SOAP? Just by using a different protocol like SMTP (I believe SMTP is stateful)? Can some one explain me teh details?
3. Also, in REST, we do not need any specific contract like WSDL am I correct? In that case, how is the service distributed to the client? In case we are converting a SOAP based service to REST based service, what the steps to be considered?
Could you provide a link to that post?
You can do whatever you like in a REST protocol. And the way that the service is distributed to the client is that the server people write some documentation and post it in a place where potential clients can see it.
Instead of learning about the protocols and how they work, you have seized on the concept of "state". Trying to learn about protocols from that point of view isn't going to work
"A day spent without the sight or sound of beauty,
the contemplation of mystery, or the search of truth or perfection is a poverty-stricken day;
and a succession of such days is fatal to human life."
Suma Rangaraj wrote:Thank you Paul for putting up with my ignorance. I will go through the article that you ahve mentioned below.
Hope I can ping if I have further questions.
You showed up just in time for the waffles! And this tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koophttps://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton