From 81ab25742a80d45d88d815adadfc61990d01fe7a Mon Sep 17 00:00:00 2001 From: Ossama Othman Date: Fri, 17 Dec 1999 01:08:41 +0000 Subject: Fixed broken hyperlinks. --- TAO/docs/pluggable_protocols/index.html | 24 ++++++++++++------------ 1 file changed, 12 insertions(+), 12 deletions(-) (limited to 'TAO/docs/pluggable_protocols') diff --git a/TAO/docs/pluggable_protocols/index.html b/TAO/docs/pluggable_protocols/index.html index 844d34236e1..cf4041f6ee4 100644 --- a/TAO/docs/pluggable_protocols/index.html +++ b/TAO/docs/pluggable_protocols/index.html @@ -248,7 +248,7 @@ Solution

We use the Acceptor pattern [1] to accept the connections. As + HREF="#Schmidt:97c">1] to accept the connections. As with the Connector pattern, an Acceptor decouples the connection establishment from the processing performed on that connection. However, in the Acceptor pattern, the connection is accepted passively, rather than being initiated actively. @@ -260,7 +260,7 @@ Applying the solution to TAO

-Figure 1 illustrates how TAO's pluggable protocols framework leverages +Figure 1 illustrates how TAO's pluggable protocols framework leverages the design presented in Section [*]. The concrete ACE Service Handler created by the ACE Acceptor is responsible @@ -809,10 +809,10 @@ Solution

We use the Connector pattern [1] to actively establish a connection + HREF="#Schmidt:97c">1] to actively establish a connection to a remote object. This pattern decouples the connection establishment from the processing performed after the connection is successful. As before, the -Connector Registry shown in Figure 2 is used +Connector Registry shown in Figure 2 is used

@@ -856,7 +856,7 @@ for the ACE implementation of the Connector pattern. Thus, they are typically lightweight objects that simply delegate to a corresponding ACE component.

-Figure 3 shows the base classes and their relations for IIOP. +Figure 3 shows the base classes and their relations for IIOP.

@@ -1607,7 +1607,7 @@ The Protocol_Factory Object

TAO's uses the ACE's Service Configurator implementation [2] + HREF="#Schmidt:94k">2] to dynamically load pluggable protocol factories. A Protocol_Factory is responsible for creating the Acceptor and Connector for the given pluggable protocol. TAO iterates through the list of loaded Protocol @@ -1968,7 +1968,7 @@ be possible to isolate them from the details of the ORB messaging implementation Care must be taken, however, because not all ORB Messaging protocols can be used with all transport protocols, i.e., some mechanism is needed to ensure only semantically compatible protocols are configured [3]. + HREF="#Johnson:95a">3].

@@ -2000,7 +2000,7 @@ Solution

Use the Layers architecture pattern [4], which decomposes + HREF="#Buschmann:95b">4], which decomposes the system into groups of components, each one at a different level of abstraction.1 For the client, the ORB uses a particular ORB messaging protocol to send a request. This ORB messaging protocol delegates part of the work to the transport @@ -2047,15 +2047,15 @@ Applying the solution in TAO

-As shown in Figure 4, TAO implements the messaging protocol +As shown in Figure 4, TAO implements the messaging protocol and the transport protocol in separate components. The client ORB uses the current profile to find the right transport and ORB messaging implementations. The creation and initialization of these classes is controlled by the Connector -(described in Section 2.2), with each Connector instance +(described in Section 2.2), with each Connector instance handling a particular ORB messaging/transport tuple.

-Figure 5 illustrates how the server's implementation uses the +Figure 5 illustrates how the server's implementation uses the same transport classes, but with a different relationship. In particular, the transport class calls back the messaging class when data is received from the IPC mechanism. As with the client, a factory, in this case the Acceptor, @@ -3014,7 +3014,7 @@ examples of the Layers architecture.

Ossama Othman
-Last modified: Thu Dec 16 19:05:58 CST 1999 +Last modified: Thu Dec 16 19:07:50 CST 1999 -- cgit v1.2.1