summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJohnny Willemsen <jwillemsen@remedy.nl>2017-02-22 14:51:01 +0100
committerJohnny Willemsen <jwillemsen@remedy.nl>2017-02-22 14:51:01 +0100
commit056104fadb504bbc7d57134e16af440a5c02bab4 (patch)
tree10600690455922c6aa7801b9ae0900c10a49ff01
parentd835f05c179b7e008f9f2708bb579a7b4810bdd4 (diff)
downloadATCD-056104fadb504bbc7d57134e16af440a5c02bab4.tar.gz
Fixed typos
* TAO/orbsvcs/orbsvcs/HTIOP/README.txt:
-rw-r--r--TAO/orbsvcs/orbsvcs/HTIOP/README.txt12
1 files changed, 6 insertions, 6 deletions
diff --git a/TAO/orbsvcs/orbsvcs/HTIOP/README.txt b/TAO/orbsvcs/orbsvcs/HTIOP/README.txt
index 7df8960f972..d4d1e86052e 100644
--- a/TAO/orbsvcs/orbsvcs/HTIOP/README.txt
+++ b/TAO/orbsvcs/orbsvcs/HTIOP/README.txt
@@ -34,7 +34,7 @@ peers to identify many different clients, which may reside on locally
similar or non-routable networks, such as 10.*.*.* or 192.168.*.*.
HTIOP_Factory - This is the service configuration class used to load
-the pluggable protocol via the ACE Service Configuratior. The
+the pluggable protocol via the ACE Service Configurator. The
HTIOP_Factory takes the following initialization arguments:
-config <filename> Specifies the text file containing HTBP specific
@@ -76,16 +76,16 @@ TAO to utilize the HTBP Protocol.
3. Directory Structure
. $ACE_ROOT/ace/HTBP
- Files used for implementing the low level HTBP Protocol.
+ Files used for implementing the low level HTBP Protocol.
. $TAO_ROOT/orbsvcs/orbsvcs/HTIOP
- Files that implements HTIOP protocol.
+ Files that implements HTIOP protocol.
. $ACE_ROOT/tests/HTBP
- Tests for the low level HTBP Protocol.
+ Tests for the low level HTBP Protocol.
. $TAO_ROOT/orbsvcs/tests/HTIOP
- Tests for the HTIOP protocol.
+ Tests for the HTIOP protocol.
4. Requirements for using HTBP Protocol
Refer to ace/HTBP/README for details on configuring HTBP clients
@@ -108,7 +108,7 @@ TAO to utilize the HTBP Protocol.
A second challenge is that while a proxy will open multiple TCP/IP
connections to a server (the outside peer), when faced with multiple
- simultanious HTTP requests, it will reuse those connections at will
+ simultaneous HTTP requests, it will reuse those connections at will
to forward any subsequent requests. This means that a socket is
associated with a particular HTIOP session for only one HTTP
request/reply.