| Home · All Classes · Grouped Classes · Annotated · Functions |
The MmsComms class is the base class for MMS communications. More...
#include <MmsComms>
Inherits QObject.
The MmsComms class is the base class for MMS communications.
The MmsComms class is the base class for MMS communications. Usually MMS communications via WAP is implemented by deriving from this class and implementing the pure virtual functions and emitting the signals when appropriate.
Constructs a MmsComms, associated with account acc and having parent object parent.
Destroys this MmsComms.
Clear any requests that are pending or in progress.
This signal must be emitted when an m-delivery-ind MMS message msg arrives via WAP PUSH.
This signal must be emitted when a fatal error occurs during the communication process, e.g. connection refused. The code code should reflect the error seen by the underlying network protocol being used. The error message msg must be a suitable for displaying to the user and refect the meaning of code.
Return true if there are requests pending or in progress, otherwise false.
Returns the default WAP networking account.
This signal must be emitted when an m-notification-ind MMS message msg arrives via WAP PUSH.
This signal must be emitted in response to a retrieveMessage(), unless an error occurrs. The MMS message msg contains the message as decoded by retrieveMessage() which has a encoded size of size.
See also error().
Connect to the MMSC and GET an MMS message from URL url. If a connection to a WAP gateway is necessary, it should be done also. The QMailAccount details can be accessed via the account variable.
See also retrieveConf().
This signal must be emitted in response to a sendMessage(), unless an error occurs. The MMS message msg contains the confirmation details and the message content as received by sendMessage() .
See also error().
Connect to the MMSC and POST the specified MMS message msg, the encoded content of which is contained in encoded. If a connection to a WAP gateway is necessary, it should be done also. The QMailAccount details can be accessed via the account variable.
See also sendConf().
This signal can be emitted when the status of a transfer changes, e.g. connected to server, transferring data. The status status could be used to provide user feed back eg: a status bar.
See also error().
This signal must be emitted during data transfers so that the user can see how much data has been transferred. size denotes the amount of data transferred in bytes.
This signal must be emitted when all pending or current transfers have completed.
| Copyright © 2008 Trolltech | Trademarks | Qtopia 4.3.2 |