equal
deleted
inserted
replaced
29 it as required. </p> <p>The following figure shows the logical structure of |
29 it as required. </p> <p>The following figure shows the logical structure of |
30 the Message Server. Dashed boxes indicate components that can be developed |
30 the Message Server. Dashed boxes indicate components that can be developed |
31 by third-parties. </p> <fig id="GUID-F469ED0A-E43F-5260-B86E-3EFE3CBA0DBB"> |
31 by third-parties. </p> <fig id="GUID-F469ED0A-E43F-5260-B86E-3EFE3CBA0DBB"> |
32 <title> Logical structure of Messaging Middleware architecture |
32 <title> Logical structure of Messaging Middleware architecture |
33 </title> |
33 </title> |
34 <image href="GUID-0259868F-8F88-5D9D-A9DE-9309C3BFBA85_d0e281248_href.png" placement="inline"/> |
34 <image href="GUID-0259868F-8F88-5D9D-A9DE-9309C3BFBA85_d0e277562_href.png" placement="inline"/> |
35 </fig><note> No lower-level communication components are shown, as the architecture |
35 </fig><note> No lower-level communication components are shown, as the architecture |
36 is designed to be independent of any particular communication protocol. Instead, |
36 is designed to be independent of any particular communication protocol. Instead, |
37 communication libraries are accessed as needed by Server MTMs. For example, |
37 communication libraries are accessed as needed by Server MTMs. For example, |
38 an SMTP MTM would use TCP/IP, while the SMS MTM would use the Telephony Server |
38 an SMTP MTM would use TCP/IP, while the SMS MTM would use the Telephony Server |
39 (ETel).</note> <dl> |
39 (ETel).</note> <dl> |