W3C home > Mailing lists > Public > public-ws-desc-eds@w3.org > April 2005

2002/ws/desc/wsdl20 wsdl20-primer.xml,1.54,1.55 wsdl20-primer.html,1.35,1.36

From: David Booth via cvs-syncmail <cvsmail@w3.org>
Date: Mon, 18 Apr 2005 03:25:14 +0000
To: public-ws-desc-eds@w3.org
Message-Id: <E1DNMss-0001JJ-5S@lionel-hutz.w3.org>

Update of /sources/public/2002/ws/desc/wsdl20
In directory hutz:/tmp/cvs-serv3403

Modified Files:
	wsdl20-primer.xml wsdl20-primer.html 
Log Message:
Finished editing/updating through sec 7.9 (GET vs POST).



Index: wsdl20-primer.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-primer.xml,v
retrieving revision 1.54
retrieving revision 1.55
diff -C2 -d -r1.54 -r1.55
*** wsdl20-primer.xml	17 Apr 2005 23:17:18 -0000	1.54
--- wsdl20-primer.xml	18 Apr 2005 03:25:11 -0000	1.55
***************
*** 1633,1637 ****
  				<p>To ensure that client and service implementations can easily determine the interface operation under which a received message was sent (even though not every client or service may need to make such a determination), it is considered good practice to follow one of the above strategies when authoring WSDL 2.0 documents.</p>
  			</div2><div2 id="adv-get-vs-post"><head>GET Versus POST: Which to Use?</head>
! 				<p>@@@@@@@@@@@@@@@@@@@@@@@@@@@@</p><p>[Add material from http://lists.w3.org/Archives/Public/www-ws-desc/2003Mar/0068.html that prescribes when to use GET versus POST as well as some useful example]</p>
  			</div2>
  
--- 1633,1637 ----
  				<p>To ensure that client and service implementations can easily determine the interface operation under which a received message was sent (even though not every client or service may need to make such a determination), it is considered good practice to follow one of the above strategies when authoring WSDL 2.0 documents.</p>
  			</div2><div2 id="adv-get-vs-post"><head>GET Versus POST: Which to Use?</head>
! 				<p> When a binding using HTTP  is specified for an operation, the WSDL 2.0 author must decide which HTTP method is appropriate to use -- usually a choice between GET and POST.  In the  context of the Web as a whole (rather than specifically Web services), the W3C Technical Architecture Group (TAG) has address the question of when it is appropriate to use GET, versus when to use POST, in a finding entitled <emph>URIs, Addressability, and the use of HTTP GET and POST</emph>   @@bibref@@.   From the abstract:</p><p><quote><emph>. . . designers should adopt [GET] for safe operations such as simple queries. POST is appropriate for other types of applications where a user request has the potential to change the state of the resource (or of related resources). The finding explains how to choose between HTTP GET and POST for an application taking into account architectural, security, and practical considerations.</emph></quote></p><p>Recall that the concept of a safe operation (i.e., invocation does not causenew obligations)  was discussed in <specref ref="more-interfaces-op-attr"/>.  Although the <code>safe</code> attribute of an interface operation indicates that the abstract operation is safe, it does not automatically cause GET to be used at the HTTP level when the binding is specified.   The choice of GET or POST is determined at the binding level: </p><ulist><item><p>If the WSDL 2.0 SOAP binding extension is used (<specref ref="more-bindings-soap"/>), with HTTP as the underlying transport protocol, then GET may be specified by setting:<glist><gitem><label><code>wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP"</code></label><def><p>on the <code>binding</code> element (to indicate the use of HTTP as the underlying protocol); and</p></def></gitem><gitem><label><code>wsoap:mep="http://www.w3.org/2003/05/soap/mep/soap-response/"</code></label><def><p>on the binding <code>operation</code> element, which causes GET to be used by default.</p></def></gitem></glist> </p></item><item><p>If the WSDL 2.0 TTP binding extension is used directly (<specref ref="more-bindings-http"/>), GET may be specified by setting either:<glist><gitem><label><code>whttp:methodDefault="GET"</code></label><def><p>on the <code>binding</code> element; or</p></def></gitem><gitem><label><code>whttp:method="GET"</code></label><def><p>on the binding <code>operation</code> element, which overrides <code>whttp:methodDefault</code> if set on the <code>binding</code> element.</p></def></gitem></glist></p></item></ulist><p>  </p>
  			</div2>
  
***************
*** 1660,1664 ****
  				</p>
  
! <div3 id="reservationDetails"><head>The Reservation Details Web Service</head>
  
  				<p>
--- 1660,1664 ----
  				</p>
  
! <p>@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@</p><div3 id="reservationDetails"><head>The Reservation Details Web Service</head>
  
  				<p>

Index: wsdl20-primer.html
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-primer.html,v
retrieving revision 1.35
retrieving revision 1.36
diff -C2 -d -r1.35 -r1.36
*** wsdl20-primer.html	17 Apr 2005 23:17:18 -0000	1.35
--- wsdl20-primer.html	18 Apr 2005 03:25:11 -0000	1.36
***************
*** 363,373 ****
  Schemas</a><br />
  &#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;7.12.1 <a
! href="#id5195262">Schemas in Imported Documents</a><br />
  &#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;7.12.2 <a
! href="#id5213617">Multiple Inline Schemas on One Document</a><br />
  &#160;&#160;&#160;&#160;7.13 <a href="#adv-schema-location">The
  schemaLocation Attribute</a><br />
  &#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;7.13.1 <a
! href="#id5212951">Using the id Attribute to Identify Inline
  Schemas</a><br />
  &#160;&#160;&#160;&#160;7.14 <a href="#adv-rdf-mapping">Mapping to
--- 363,373 ----
  Schemas</a><br />
  &#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;7.12.1 <a
! href="#id5213157">Schemas in Imported Documents</a><br />
  &#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;7.12.2 <a
! href="#id5213460">Multiple Inline Schemas on One Document</a><br />
  &#160;&#160;&#160;&#160;7.13 <a href="#adv-schema-location">The
  schemaLocation Attribute</a><br />
  &#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;7.13.1 <a
! href="#id5213768">Using the id Attribute to Identify Inline
  Schemas</a><br />
  &#160;&#160;&#160;&#160;7.14 <a href="#adv-rdf-mapping">Mapping to
***************
*** 4484,4493 ****
  Versus POST: Which to Use?</h3>
  
! <p>@@@@@@@@@@@@@@@@@@@@@@@@@@@@</p>
  
! <p>[Add material from
! http://lists.w3.org/Archives/Public/www-ws-desc/2003Mar/0068.html
! that prescribes when to use GET versus POST as well as some useful
! example]</p>
  </div>
  
--- 4484,4565 ----
  Versus POST: Which to Use?</h3>
  
! <p>When a binding using HTTP is specified for an operation, the
! WSDL 2.0 author must decide which HTTP method is appropriate to use
! -- usually a choice between GET and POST. In the context of the Web
! as a whole (rather than specifically Web services), the W3C
! Technical Architecture Group (TAG) has address the question of when
! it is appropriate to use GET, versus when to use POST, in a finding
! entitled <em>URIs, Addressability, and the use of HTTP GET and
! POST</em> @@bibref@@. From the abstract:</p>
  
! <p>"<em>. . . designers should adopt [GET] for safe operations such
! as simple queries. POST is appropriate for other types of
! applications where a user request has the potential to change the
! state of the resource (or of related resources). The finding
! explains how to choose between HTTP GET and POST for an application
! taking into account architectural, security, and practical
! considerations.</em>"</p>
! 
! <p>Recall that the concept of a safe operation (i.e., invocation
! does not cause new obligations) was discussed in <a
! href="#more-interfaces-op-attr"><b>5.4.1 Operation
! Attributes</b></a>. Although the <code>safe</code> attribute of an
! interface operation indicates that the abstract operation is safe,
! it does not automatically cause GET to be used at the HTTP level
! when the binding is specified. The choice of GET or POST is
! determined at the binding level:</p>
! 
! <ul>
! <li>
! <p>If the WSDL 2.0 SOAP binding extension is used (<a
! href="#more-bindings-soap"><b>6.5 The SOAP Binding
! Extension</b></a>), with HTTP as the underlying transport protocol,
! then GET may be specified by setting:</p>
! 
! <dl>
! <dt class="label">
! <code>wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP"</code></dt>
! 
! <dd>
! <p>on the <code>binding</code> element (to indicate the use of HTTP
! as the underlying protocol); and</p>
! </dd>
! 
! <dt class="label">
! <code>wsoap:mep="http://www.w3.org/2003/05/soap/mep/soap-response/"</code></dt>
! 
! <dd>
! <p>on the binding <code>operation</code> element, which causes GET
! to be used by default.</p>
! </dd>
! </dl>
! 
! <p></p>
! </li>
! 
! <li>
! <p>If the WSDL 2.0 HTTP binding extension is used directly (<a
! href="#more-bindings-http"><b>6.6 The HTTP Binding
! Extension</b></a>), GET may be specified by setting either:</p>
! 
! <dl>
! <dt class="label"><code>whttp:methodDefault="GET"</code></dt>
! 
! <dd>
! <p>on the <code>binding</code> element; or</p>
! </dd>
! 
! <dt class="label"><code>whttp:method="GET"</code></dt>
! 
! <dd>
! <p>on the binding <code>operation</code> element, which overrides
! <code>whttp:methodDefault</code> if set on the <code>binding</code>
! element.</p>
! </dd>
! </dl>
! </li>
! </ul>
! 
! <p></p>
  </div>
  
***************
*** 4525,4528 ****
--- 4597,4604 ----
  are the Web service analogs of document hyperlinks.</p>
  
+ <p>@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
+ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
+ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@</p>
+ 
  <div class="div3">
  <h4><a id="reservationDetails" name="reservationDetails"></a>7.10.1
Received on Monday, 18 April 2005 03:25:14 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:31:34 UTC