锘??xml version="1.0" encoding="utf-8" standalone="yes"?>亚洲av午夜精品一区二区三区 ,亚洲a级在线观看,亚洲色大成网站WWW久久九九http://m.tkk7.com/ldd600/category/32142.html璺極婕叾淇繙鍏紝鍚懼皢涓婁笅鑰屾眰绱?/description>zh-cnSat, 15 Aug 2009 16:15:30 GMTSat, 15 Aug 2009 16:15:30 GMT60java绔疪ESTful web services鐨勫嚑縐嶅疄鐜版柟寮?/title><link>http://m.tkk7.com/ldd600/archive/2009/08/13/291018.html</link><dc:creator>鍙卞挙綰漢</dc:creator><author>鍙卞挙綰漢</author><pubDate>Thu, 13 Aug 2009 07:27:00 GMT</pubDate><guid>http://m.tkk7.com/ldd600/archive/2009/08/13/291018.html</guid><wfw:comment>http://m.tkk7.com/ldd600/comments/291018.html</wfw:comment><comments>http://m.tkk7.com/ldd600/archive/2009/08/13/291018.html#Feedback</comments><slash:comments>0</slash:comments><wfw:commentRss>http://m.tkk7.com/ldd600/comments/commentRss/291018.html</wfw:commentRss><trackback:ping>http://m.tkk7.com/ldd600/services/trackbacks/291018.html</trackback:ping><description><![CDATA[     鎽樿: java绔疪ESTful web services鐨勫嚑縐嶅疄鐜版柟寮?nbsp; <a href='http://m.tkk7.com/ldd600/archive/2009/08/13/291018.html'>闃呰鍏ㄦ枃</a><img src ="http://m.tkk7.com/ldd600/aggbug/291018.html" width = "1" height = "1" /><br><br><div align=right><a style="text-decoration:none;" href="http://m.tkk7.com/ldd600/" target="_blank">鍙卞挙綰漢</a> 2009-08-13 15:27 <a href="http://m.tkk7.com/ldd600/archive/2009/08/13/291018.html#Feedback" target="_blank" style="text-decoration:none;">鍙戣〃璇勮</a></div>]]></description></item><item><title>RESTful vs SOAPyhttp://m.tkk7.com/ldd600/archive/2009/07/31/289209.html鍙卞挙綰漢鍙卞挙綰漢Fri, 31 Jul 2009 00:40:00 GMThttp://m.tkk7.com/ldd600/archive/2009/07/31/289209.htmlhttp://m.tkk7.com/ldd600/comments/289209.htmlhttp://m.tkk7.com/ldd600/archive/2009/07/31/289209.html#Feedback0http://m.tkk7.com/ldd600/comments/commentRss/289209.htmlhttp://m.tkk7.com/ldd600/services/trackbacks/289209.htmlRest and Restful web services

There are currently two schools of thought in developing web services: the traditional, standards-based approach (SOAP) and conceptually simpler and the trendier new kid on the block (REST). The origin of the term "REST" comes from the famous thesis from Roy Fielding describing the concept of Representative State Transfer (REST). REST is an architectural style that can be summed up as four verbs (GET, POST, PUT, and DELETE from HTTP 1.1) and the nouns, which are the resources available on the network (referenced in the URI). The verbs have the following operational equivalents:

HTTP     CRUD Equivalent

==============================

GET      read

POST     create,update,delete

PUT      create,update

DELETE   delete

The emergence of the RESTful style of web services was a reaction to the more heavy-weight SOAP-based standards. In RESTful web services, the emphasis is on simple point-to-point communication over HTTP using plain old XML (POX) or JSON.

Java API for RESTful Web Services specification is in final state, JAX-RS is an annotation-based API for implementing RESTful web services, based on HTTP. In addition to the Sun-provided reference implementation, Jersey, other implementations are available (in various stages of completion): as part of the popular Restlet framework, the JBoss RESTeasy project , and as part of the Apache CXF web services stack.

Rest vs SOAP:

Representation

A REST-style web service might be every bit as subtle and complicated as a SOAP-based service. The RESTful approach tries to simplify matters by taking what HTTP, with its MIME type system, already offers: built-in CRUD operations, uniformly identifiable resources, and typed representations that can capture a resource's state. The key to the REST methodology is to write Web services using a representation that is already well known and widely used: the URI.

Complexity

REST as a design philosophy tries to isolate application complexity at the endpoints, that is, at the client and at the service. A service may require lots of logic and computation to maintain resources and to generate adequate representation of resources鈥攆or instance, large and subtly formatted XML documents鈥攁nd a client may require significant XML processing to extract the desired information from the XML representations transferred from the service to the client.

Bandwidth

RESTful approach keeps the complexity out of the transport level, as a resource representation is transferred to the client as the body of an HTTP response message. By contrast, a SOAP-based service inevitably complicates the transport level because a SOAP message is encapsulated as the body of a transport message; for instance, an HTTP or SMTP message. SOAP requires messages within messages, whereas REST does not.

Performance

SOAP uses XML generally bloats your messages quite a bit.

Something like POX or JSON would be more compact and maybe faster to serialize / deserialize.

Payloads of SOAP are significantly larger which are slower to assemble, transport, parse, validate and process.

Security

A typical SOAP request will use POST to communicate with a given service. And without looking into the SOAP envelope, there's no way to know whether that request simply wants to query data or delete entire tables from the database

As for authentication and authorization, SOAP places the burden in the hands of the application developer. The REST methodology instead takes into account the fact that Web servers already have support for these tasks.

Domain Design

SOAP services defined in Web Services Description Language (WSDL) emphasize contracts and actions. In contrast, REST focuses on direct addressing and manipulation of resources, which is more compatible with the domain-driven approach.

Defects

l           There is less definition of interface, especially the method interface

l           Hard to make strongly typed objects to work with it in server side code  

l           Only works over HTTP, but SOAP can work on HTTP, FTP, MIME, JMS, SMTP and etc

l           Calls to REST are restricted by HTTP Verbs (GET, POST, PUT, DELETE.. etc)

l           No automatic xml schema validation

l           Less SOA-style than SOAP

l           Developer has less control on security than SOAP, SOAP has ws-*(ws-security, ws-trust, ws-policy and etc), SAML, XACML and etc

l           Routing is network-controlled, but SOAP can make client to control routing explicitly through SOAP headers, WS-Addressing and etc

Implementation

How to implement Restful web services, there are three kinds of methods recently:

  • Make use of provider and dispatch twins of SOAP-based web service
  • Implement Restful HTTPServlets
  • JAX-RS, annotation-based implementation


]]>
主站蜘蛛池模板: 精品一区二区三区无码免费视频| 91在线视频免费观看| 91免费播放人人爽人人快乐| 亚洲av无码一区二区三区乱子伦| a级毛片毛片免费观看久潮| 国内精品久久久久久久亚洲| 中文字幕免费人成乱码中国| 亚洲色偷偷偷鲁综合| 波多野结衣免费一区视频| 亚洲国产另类久久久精品| 男女作爱在线播放免费网站| 亚洲高清美女一区二区三区| 免费成人激情视频| 亚洲色大成网站WWW国产| 国产美女精品视频免费观看| 国产精品亚洲色图| 国产精品亚洲mnbav网站 | 中文字幕亚洲乱码熟女一区二区 | 亚洲成AⅤ人影院在线观看| 日韩在线视频播放免费视频完整版| 亚洲av无码成人精品区| a级特黄毛片免费观看| 精品亚洲成a人片在线观看少妇| 午夜国产精品免费观看| 亚洲av无码一区二区三区四区| 亚洲日本一区二区一本一道| 国产午夜无码精品免费看| 91亚洲自偷在线观看国产馆| 在线永久免费观看黄网站| 中文字幕乱理片免费完整的| 亚洲老熟女@TubeumTV| 日韩a级毛片免费观看| 中文字幕免费在线视频| 亚洲人成毛片线播放| 亚洲成AV人在线观看网址| 久久一区二区三区免费播放| 亚洲三级高清免费| 亚洲综合无码AV一区二区| 青娱分类视频精品免费2| 一级毛片免费全部播放| 亚洲国产精品网站久久|