46 directly. They come over other subsystems to the BIO database. For example, |
46 directly. They come over other subsystems to the BIO database. For example, |
47 the SMS watchers receive BIO messages from the SMS stack and use BIO Messaging |
47 the SMS watchers receive BIO messages from the SMS stack and use BIO Messaging |
48 Framework to tag the messages with the correct BIO ID. </p> <p>The following |
48 Framework to tag the messages with the correct BIO ID. </p> <p>The following |
49 figure illustrates the BIO Messaging Framework architecture: </p> <fig id="GUID-2CEE40B9-2559-5CF3-B98F-2472F6B4D35D"> |
49 figure illustrates the BIO Messaging Framework architecture: </p> <fig id="GUID-2CEE40B9-2559-5CF3-B98F-2472F6B4D35D"> |
50 <title> BIO Messaging Framework architecture </title> |
50 <title> BIO Messaging Framework architecture </title> |
51 <image href="GUID-42609A21-CEDC-58E8-864C-0CF8458F6798_d0e290725_href.png" placement="inline"/> |
51 <image href="GUID-42609A21-CEDC-58E8-864C-0CF8458F6798_d0e287092_href.png" placement="inline"/> |
52 </fig> <p id="GUID-38031091-ED66-51CF-A025-85C7CEEC3D7D"><b>BIO database</b> </p> <p>The |
52 </fig> <p id="GUID-38031091-ED66-51CF-A025-85C7CEEC3D7D"><b>BIO database</b> </p> <p>The |
53 BIO database is used to identify the type of BIO messages. It maps message |
53 BIO database is used to identify the type of BIO messages. It maps message |
54 attributes, such as port number, MIME type, or leading string to a BIO type. |
54 attributes, such as port number, MIME type, or leading string to a BIO type. |
55 These attributes are then used by clients of the BIO Message Framework to |
55 These attributes are then used by clients of the BIO Message Framework to |
56 determine what ports to listen for messages. For example, SMS messages which |
56 determine what ports to listen for messages. For example, SMS messages which |