ORG.BLUEZ.OBEX.MESSAGEACCESS(5) | Linux System Administration | ORG.BLUEZ.OBEX.MESSAGEACCESS(5) |
org.bluez.obex.MessageAccess - BlueZ D-Bus OBEX MessageAccess API documentation
Possible name:
Possible errors:
Possible filter:
Possible return:
Possible errors:
Possible values:
Possible errors: None
Possible Filters:
uint16 MaxCount (default 1024):
See ListFilterFields() for possible values.
Possible values:
Possible values:
Possible values:
Possible values:
Possible values:
Each message is represented by an object path, which implements org.bluez.obex.Message(5) interface, followed by a dictionary of its properties.
void UpdateInbox(void)
The message is transferred either to the given subfolder of the current folder, or to the current folder if folder is empty.
Possible args: Transparent, Retry, Charset
The returned path represents the newly created transfer, which should be used to find out if the content has been successfully transferred or if the operation fails.
The properties of this transfer are also returned along with the object path, to avoid a call to GetProperties, see org.bluez.obex.Transfer(5) for the possible list of properties.
Possible errors:
October 2023 | BlueZ |