You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ws.apache.org by to...@apache.org on 2004/10/04 13:27:57 UTC
cvs commit: ws-site/targets/axis/java client-side-axis.html client-side-axis.pdf
toshi 2004/10/04 04:27:57
Modified: targets/axis/java client-side-axis.html client-side-axis.pdf
Log:
Correcting a doc-bug reported by Ron Wheeler (rwheeler@artifact-software.com)
Revision Changes Path
1.4 +2 -2 ws-site/targets/axis/java/client-side-axis.html
Index: client-side-axis.html
===================================================================
RCS file: /home/cvs/ws-site/targets/axis/java/client-side-axis.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- client-side-axis.html 13 Jul 2004 10:00:28 -0000 1.3
+++ client-side-axis.html 4 Oct 2004 11:27:57 -0000 1.4
@@ -287,7 +287,7 @@
<h4>Core TCP/IP Concepts</h4>
</div>
<p>We are not going to explain TCP/IP in any detail, as it is far too complex. Some of the concepts and features of the technology are worth covering.</p>
-<p>TCP/IP builds a reliable channel between two computers, <em>hosts</em>. Every computer running TCP can receive messages coming in on any <em>port</em>, from 1-65535. That is, if a program on that machine has created a <em>socket</em> and is listening on that port. If not, you will see the message, from 1-65535. That is, if a program on that machine has created a <em>socket</em> and is listening on that port. If not, you will see the message <em>connection refused.</em>
+<p>TCP/IP builds a reliable channel between two computers, <em>hosts</em>. Every computer running TCP can receive messages coming in on any <em>port</em>, from 1-65535. That is, if a program on that machine has created a <em>socket</em> and is listening on that port. If not, you will see the message <em>connection refused.</em>
</p>
<p>Before a client connects to a host, it has to find its address. IPv4, the most widely supported version of TCP/IP uses 32 bit addresses, such as 127.0.0.1 (that's a special address, it means the local system). To connect to a host you need either the address, or a name of machine "www.w3.org" that can get mapped to an address. That mapping is provided by DNS, a hierarchical network that is so ubiquitous across the infrastructure that we usually take it for granted. Essentially, DNS servers take a hostname and return an IP address or an error message. How DNS servers work out the address is beyond the scope of this document; just assume that a local DNS server asks other ones if it thinks it needs to.</p>
<p>Not all systems have DNS support. A system can be configured to have its own host table; on Unix systems this lives in /etc/hosts, on windows in c:\windows\system32\drivers\etc\hosts. You can edit this file and bypass DNS completely, creating a maintenance nightmare in the process. If your users use static host tables rather than DNS, you can never change the network address of a host without serious grief.</p>
@@ -303,7 +303,7 @@
</li>
</ol>
<p>When communicating over a network, <em>latency</em> and <em>bandwidth</em> are the big constraints. Latency is how long it takes to communicate -all those bits of hardware like routers and firewalls add to latency, as does the network wiring. Bandwidth is the measure of how much stuff you can send per second. A link with low latency (good) may still have low bandwidth (bad), while a high bandwidth connection might have a high latency, as the remote server is distant.</p>
-<p>Firewalls are a critical feature of modern networks. A firewall blocks off ports to incoming calls. AFirewalls are a critical feature of modern networks. A firewall blocks off ports to incoming calls. A <em>stateful firewall</em>examines every packet and only allows packets of the current TCP conversation in, and is even better. Firewalls are essential for security reasons, so that you can expose more services behind a network than to the outside world. As well as restricting incoming calls, they often restrict outbound connections. For example, outbound connections to port 80 (HTTP) may be blocked to encourage use of an HTTP proxy server (see below), outbound connections to port 143 (IMAP) blocked to stop people connecting to external mail servers. You need to assume that there will be firewalls in the network, between SOAP client and server, and so callbacks from server to client are not going to be possible.examines every packet and only allows packets of the current TCP conversation in, and is even better. Firewalls are essential for security reasons, so that you can expose more services behind a network than to the outside world. As well as restricting incoming calls, they often restrict outbound connections. For example, outbound connections to port 80 (HTTP) may be blocked to encourage use of an HTTP proxy server (see below), outbound connections to port 143 (IMAP) blocked to stop people connecting to external mail servers. You need to assume that there will be firewalls in the network, between SOAP client and server, and so callbacks from server to client are not going to be possible.</p>
+<p>Firewalls are a critical feature of modern networks. A firewall blocks off ports to incoming calls. A stateful firewall examines every packet and only allows packets of the current TCP conversation in, and is even better. Firewalls are essential for security reasons, so that you can expose more services behind a network than to the outside world. As well as restricting incoming calls, they often restrict outbound connections. For example, outbound connections to port 80 (HTTP) may be blocked to encourage use of an HTTP proxy server (see below), outbound connections to port 143 (IMAP) blocked to stop people connecting to external mail servers. You need to assume that there will be firewalls in the network, between SOAP client and server, and so callbacks from server to client are not going to be possible.</p>
<div class="h4">
<h4>Core HTTP Concepts</h4>
</div>
1.3 +130 -130 ws-site/targets/axis/java/client-side-axis.pdf
<<Binary file>>