c# - Converting asmx SOAP webservice to REST on ASP.NET: is WCF really useful for just that ? -
why not add http support in config , that's done advantage service dual both soap , rest?
what's buzz around rest ? wcf bring ?
i mean what's difference from viewpoint of rest client application if set in web.config asmx webservice being able accept rest-like syntax
<webservices> <protocols> <add name="httpget" /> </protocols> </webservices>
and wcf rest implementation http://geekswithblogs.net/.netonmymind/archive/2008/02/04/119291.aspx ?
seems nobody can answer ... because it's hard or question stupid :)
client sees url (encapsulation principle) why bother more ? , what's more that's still not clear :)
other problem: if switch wcf, need change url ? if yes means our hundred partners clients broken , i'll have notify them of our change ?
wcf nothing rest. can build own rest services without using wcf & soap stuff.. check out sample rest service build in .net 2.0
and check out excellent .net open source rest implementation
to understand more rest, read these
- http://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm
- http://en.wikipedia.org/wiki/representational_state_transfer
- what restful programming?
- rest / soap endpoints wcf service
- understanding rest: verbs, error codes, , authentication
to comment:
if have asmx webservice can converted rest in 1 line of configuration file ?
asmx services build upon soap, 1 more layer on http. rest http based, can access(or call) business resources way access normal urls. no more abstractions.
in rest, resources identified persistent identifiers(urls).
for ex in products catalog system, using asmx create set of functions add,update,delete products. addproduct(),updateproduct, etc..
but in rest, having single point of access, http:\mysystem\prodcuts. retrieve,add,update,delete products, using respective http verbs (get,post,put,delete) on same url.
so cannot convert asmx rest, since both solves problems in different way.
Comments
Post a Comment