« Uploading Input Type=File To REST WCF Service | Main | Windward Code War One - Tomas' Perspective, or What the #%$& was the Yellow Guy Thinking? »



Feed You can follow this conversation by subscribing to the comment feed for this post.

hi , Thanks for this nice article but can you explain what is major difference between REST and Axis or Soap which were earlier method of using web services ?

How Classpath works in Java

REST is short for "using the bloody HTTP spec. property".

That's all anyone needs to say on the subject.

Yes, one can say it is simple http spec.

REST can make more professional(some time this may be easier) by using rest features like,
using PUT,GET,POST for operations like Add, Read, Update
encoding parameters in the url it self
and if looking forward find few best practices here http://www.xfront.com/sld059.htm

@Javin: I'm not familiar with axis, but with SOAP, you basically make an xml document that specifies a method and actual parameters, and you send that as the http request body. The response contains the return value and data in a similar xml document in the response body.

I was curious to see what RESTful was about and found this. It looks like you described AJAX in a nutshell. Is that what I can say about REST? Getting http data from the server using whatever xml they use?

Well, they do feel similar, and I think that's because REST tries to stay close to HTTP, not complicating it. But AJAX, as I'm sure you know, is more a technique for doing asynchronous HTTP requests, so that you can do things like flicker-free updates to portions of a web page. REST is more about keeping your API close to HTTP so that you're not fighting against it, and so that you get a more symbiotic relationship. For developers, this means easy-to-use web services, and for companies offering RESTful web services, I think that translates into more money.

The comments to this entry are closed.


  • meowkins

Windward Reports


  • Quantcast