43 is supported for the construction of messages. An additional API is provided |
43 is supported for the construction of messages. An additional API is provided |
44 for sending attachments without the need to create a copy of the attachment |
44 for sending attachments without the need to create a copy of the attachment |
45 in the message store. Unlike many other MTMs, after OBEX tries to send a message, |
45 in the message store. Unlike many other MTMs, after OBEX tries to send a message, |
46 the message is deleted from the outbox whether the sending succeeds or fails. </p> <fig id="GUID-251B613E-3FF9-5219-A9FA-F6D82B77979D"> |
46 the message is deleted from the outbox whether the sending succeeds or fails. </p> <fig id="GUID-251B613E-3FF9-5219-A9FA-F6D82B77979D"> |
47 <title> OBEX MTM class diagram </title> |
47 <title> OBEX MTM class diagram </title> |
48 <image href="GUID-A7EDCB44-9E73-5FD9-B6FB-AE0BAFDC1213_d0e469977_href.jpg" placement="inline"/> |
48 <image href="GUID-A7EDCB44-9E73-5FD9-B6FB-AE0BAFDC1213_d0e475813_href.jpg" placement="inline"/> |
49 </fig> <p><b>IR MTM</b> </p> <p>The generic OBEX MTM functionality is provided |
49 </fig> <p><b>IR MTM</b> </p> <p>The generic OBEX MTM functionality is provided |
50 by the OBEX MTM DLLs, the IR MTM itself just sets up the parameters. The IR |
50 by the OBEX MTM DLLs, the IR MTM itself just sets up the parameters. The IR |
51 MTM supports non-standard OBEX transfer to maintain compatibility with older |
51 MTM supports non-standard OBEX transfer to maintain compatibility with older |
52 versions of Microsoft Windows, for example, Windows 98. The non-standard OBEX |
52 versions of Microsoft Windows, for example, Windows 98. The non-standard OBEX |
53 transfer is attempted only if the standard OBEX transfer has failed. </p> <p><b>Bluetooth |
53 transfer is attempted only if the standard OBEX transfer has failed. </p> <p><b>Bluetooth |