Soap Vs Restful Services

[KadapaKingg]

[quote name='ZuniorVentiyar' timestamp='1349228946' post='1302575527']
mama ... REST and SOAP lo nakau konni doubts unayii .... neeku time untee kodiga help cheyavaaaa .....

SAAJ lanti similar implementation emanna undha rest lo or payload lo attachments part gaa pampiancalaa ....

security using authentication or HTTPS kakundaaa certification based authentication REST lo ela implement seyali mama

REST lo SOAP acknowledge laa emina acknowledge machanisam undhaa mama .....

REST ni HTTP kakundaa inka eminaa protocols lo use cheyachaaa mama
[/quote]

Kottaga nerchukuntunnattunnav REST.. answers choodu kinda [b][color=#ff0000]RED [/color][/b]lo..

SAAJ lanti similar implementation emanna undha rest lo or payload lo attachments part gaa pampiancalaa ....

[b][color=#ff0000]No such API.. Use content type [font=Arial,]content-type:gzip or mime and return zip files/ binary data...[/font][/color][/b]

security using authentication or HTTPS kakundaaa certification based authentication REST lo ela implement seyali mama

[b][color=#ff0000][font=Arial,]Set up your own certificate authority, create root certificate, and create client certificates for the client services and give them to clients or use a time based token and use Md5 or hex of that in URL[/font][/color][/b]

REST lo SOAP acknowledge laa emina acknowledge machanisam undhaa mama .....

[b][color=#ff0000]All REST interactions are by default stateless.. But if you want you can send a URL in the response that the client can use to acknowledge. We are using that in our current project.. See this example below.[/color][/b]
[b][url="http://reststar.wordpress.com/2009/11/13/reliable-acknowledgement/"][color=#ff0000]http://reststar.wordpress.com/2009/11/13/reliable-acknowledgement/[/color][/url][/b]

REST ni HTTP kakundaa inka eminaa protocols lo use cheyachaaa mama

[b][color=#ff0000]REST is a specification that can work independent of HTTP but 99.9% of time people use it with HTTP. But you can use it with other protocols like CIMP.. [/color][url="http://en.wikipedia.org/wiki/Common_management_information_protocol"][color=#ff0000]http://en.wikipedia.org/wiki/Common_management_information_protocol[/color][/url][/b]

[ChampakDas]

GP...Amazon rawks ahey
[quote name='HAPPYNESS' timestamp='1349227110' post='1302575382']
[size=5][b] ardam ayena vallu chaduvukondi..kaani vallu repost ani nannu raayuchukuni kotti vellipondi[/b]



[b] REST vs SOAP Web Services[/b][/size]


[size=5][color=#000000][font=Helvetica, Arial, sans-serif]I am seeing a lot of new web services are implemented using a [b]REST[/b] style architecture these days rather than a SOAP one. Lets step back a second and explain what REST is.
[b]What is a REST Web Service[/b]
The acronym REST stands for [i]Representational State Transfer[/i], this basically means that each unique URL is a representation of some object. You can get the contents of that object using an HTTP GET, to delete it, you then might use a POST, PUT, or DELETE to modify the object (in practice most of the services use a POST for this).
[b]Who's using REST?[/b]
All of Yahoo's web services use REST, including Flickr, del.icio.us API uses it, pubsub, bloglines, technorati, and both eBay, and Amazon have web services for both REST and SOAP.
[b]Who's using SOAP?[/b]
Google seams to be consistent in implementing their web services to use SOAP, with the exception of Blogger, which uses XML-RPC. You will find SOAP web services in lots of enterprise software as well.
[b]REST vs SOAP[/b]
As you may have noticed the companies I mentioned that are using REST api's haven't been around for very long, and their apis came out this year mostly. So REST is definitely the trendy way to create a web service, if creating web services could ever be trendy (lets face it you use soap to wash, and you rest when your tired). The main advantages of REST web services are:[/font][/color][/size][list]
[*][size=5][color=#000000][font=Helvetica, Arial, sans-serif]Lightweight - not a lot of extra xml markup[/font][/color][/size]
[*][size=5][color=#000000][font=Helvetica, Arial, sans-serif]Human Readable Results[/font][/color][/size]
[*][size=5][color=#000000][font=Helvetica, Arial, sans-serif]Easy to build - no toolkits required[/font][/color][/size]
[/list]
[size=5][color=#000000][font=Helvetica, Arial, sans-serif]SOAP also has some advantages:[/font][/color][/size][list]
[*][size=5][color=#000000][font=Helvetica, Arial, sans-serif]Easy to consume - sometimes[/font][/color][/size]
[*][size=5][color=#000000][font=Helvetica, Arial, sans-serif]Rigid - type checking, adheres to a contract[/font][/color][/size]
[*][size=5][color=#000000][font=Helvetica, Arial, sans-serif]Development tools[/font][/color][/size]
[/list]
[size=5][color=#000000][font=Helvetica, Arial, sans-serif]For consuming web services, its sometimes a toss up between which is easier. For instance Google's AdWords web service is really hard to consume (in CF anyways), it uses SOAP headers, and a number of other things that make it kind of difficult. On the converse, Amazon's REST web service can sometimes be tricky to parse because it can be highly nested, and the result schema can vary quite a bit based on what you search for.[/font][/color][/size]
[/quote]

[Gachibowli_Diwakar]

[img]http://lh6.ggpht.com/-xZXyeYxtAK8/UAHWoQ1fhgI/AAAAAAAAHGE/msEPCOlLfvE/s150/MS.gif[/img]