28 scheduler which remains active while the phone is switched on. </p> <p>The |
28 scheduler which remains active while the phone is switched on. </p> <p>The |
29 watcher executable is has the capabilities necessary for write-access to the <b>Messaging |
29 watcher executable is has the capabilities necessary for write-access to the <b>Messaging |
30 Outbox </b> folder. For instance, to update a delivery report, it may require |
30 Outbox </b> folder. For instance, to update a delivery report, it may require |
31 an entry in the Outbox to be updated. </p> <fig id="GUID-B1A76302-6F78-50A1-B5CF-B7FB670A4477"> |
31 an entry in the Outbox to be updated. </p> <fig id="GUID-B1A76302-6F78-50A1-B5CF-B7FB670A4477"> |
32 <title> Watcher Framework architecture </title> |
32 <title> Watcher Framework architecture </title> |
33 <image href="GUID-C4945844-643F-5479-AA2C-61C35817555A_d0e495755_href.jpg" placement="inline"/> |
33 <image href="GUID-C4945844-643F-5479-AA2C-61C35817555A_d0e493587_href.jpg" placement="inline"/> |
34 </fig> <p>A watcher plug-in typically make requests to another subsystem such |
34 </fig> <p>A watcher plug-in typically make requests to another subsystem such |
35 that they are completed when an external event (an SMS) being received occurs. |
35 that they are completed when an external event (an SMS) being received occurs. |
36 When a watcher has completed processing the request it waits for the next |
36 When a watcher has completed processing the request it waits for the next |
37 event. </p> </section> |
37 event. </p> </section> |
38 <section><title>API summary</title> <p>The <xref href="GUID-2C666512-BA5C-31FC-A226-9C5449A73711.dita"><apiname>CWatcherLog</apiname></xref> class |
38 <section><title>API summary</title> <p>The <xref href="GUID-2C666512-BA5C-31FC-A226-9C5449A73711.dita"><apiname>CWatcherLog</apiname></xref> class |