axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r232204 - /webservices/axis/trunk/java/xdocs/http-transport.html
Date Fri, 12 Aug 2005 04:50:15 GMT
Author: chinthaka
Date: Thu Aug 11 21:49:56 2005
New Revision: 232204

Applying HTTP transport patch for Saminda


Modified: webservices/axis/trunk/java/xdocs/http-transport.html
--- webservices/axis/trunk/java/xdocs/http-transport.html (original)
+++ webservices/axis/trunk/java/xdocs/http-transport.html Thu Aug 11 21:49:56 2005
@@ -1,9 +1,43 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<title>HTTP transports</title>
+  <title>HTTP transports</title>
-<h1><a name="#configTransport">HTTP transports</a></h1>
-<p>The HTTP is configured by default, the server can be started by following </p>
-<code>Java org.apache.axis2.transport.http.SimpleHTTPServer repository port</code>
\ No newline at end of file
+<h1><a name="#configTransport">HTTP
+<p>This is the default transport
+sender that is being used in Server API as well as Client
+funtionality of the Sender is based on commons-httpclient-3.0-rc2. In
+order to aquire the maxium flexibiliy, this sender has implemented POST
+interface and GET interface. This is mainly due to the fact that Axis2
+SOAP stack has the tendency to support REST based services as well. </p>
+Chunking support and KeepAlive support also integrated via the
+facilities provided by commons. It has the tendency to support HTTP
+version 1.0 and 1.1. As Chunking support is only available in HTTP
+version 1.1, thus, this distiction in sperating the tranport version
+is important.
+Tranport Sender sets in the axis2.xml's
+element, and it's being declared as follows,
+<pre>&lt;transportSender name="http" class="org.apache.axis2.transport.http.CommonsHTTPTransportSender"&gt;<br>
&lt;parameter name="PROTOCOL" locked="xsd:false"&gt;HTTP/1.1&lt;/parameter&gt;<br>
&lt;parameter name="Transfer-Encoding"&gt;chunked&lt;/parameter&gt;<br>&lt;/transportSender&gt;<br></pre>
+<p>Above code snippet shows the
+complete configuration of the transport sender.
+&lt;parameter/&gt; element introduces the additional paraments
+that should be complient with the sender. HTTP PROTOCOL version sets as
+HTTP/1.0 or HTTP/1.1. Default version is HTTP/1.1. It should be noted
+that Chunking support is available at HTTP/1.1. Thus, the user should
+be careful of setting the "chunked" property only with version 1.1.
+KeepAlive is default in version 1.1.&nbsp;</p>
+<p>These are the only paramenters
+that is available from deployment. Other parameters such as character
+encoding style etc, are provided via MessageContext. </p>

View raw message