精彩的人生

          好好工作,好好生活

          BlogJava 首頁 新隨筆 聯系 聚合 管理
            147 Posts :: 0 Stories :: 250 Comments :: 0 Trackbacks

          I am seeing a lot of new web services are implemented using a REST style architecture these days rather than a SOAP one. Lets step back a second and explain what REST is.

          What is a REST Web Service

          The acronym REST stands for Representational State Transfer, 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).

          Who's using REST?

          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.

          Who's using SOAP?

          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.

          REST vs SOAP

          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:

          • Lightweight - not a lot of extra xml markup
          • Human Readable Results
          • Easy to build - no toolkits required

          SOAP also has some advantages:

          • Easy to consume - sometimes
          • Rigid - type checking, adheres to a contract
          • Development tools

          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.

          Which ever architecture you choose make sure its easy for developers to access it, and well documented.




          原文:http://www.petefreitag.com/item/431.cfm

          posted on 2006-08-31 17:21 hopeshared 閱讀(1324) 評論(0)  編輯  收藏 所屬分類: Web Service
          主站蜘蛛池模板: 南宁市| 锡林浩特市| 新平| 八宿县| 芒康县| 西盟| 商城县| 贵南县| 宝清县| 莲花县| 六盘水市| 文化| 杭锦旗| 武川县| 昆山市| 柳林县| 博客| 富川| 龙里县| 招远市| 丰城市| 太仓市| 吐鲁番市| 凌源市| 孝义市| 安龙县| 汶上县| 平泉县| 辰溪县| 徐水县| 华蓥市| 阳泉市| 蕉岭县| 绥中县| 信宜市| 大英县| 宿迁市| 桂平市| 筠连县| 贵德县| 开远市|