org.bluez...ObjectPush(5)
π NAME π
Okay bestie, welcome to org.bluez.obex.ObjectPush β it's the BlueZ D-Bus OBEX ObjectPush API documentation. This is the org.bluez...ObjectPush(5) page from the Linux System Administration manual, and it's giving very specific D-Bus energy. π¦β¨
π INTERFACE π
Here's the identity card, no cap:
π«Ά Service
- Service β
org.bluez.obex
π¦ Interface
- Interface β
org.bluez.obex.ObjectPush1
π Object path
- Object path β
[Session object path]
β¨ METHODS β¨
These are the methods, bestie β each one returns an object, dict, and the object path is the transfer you watch. π
π object, dict SendFile(string sourcefile)
Sends local file to the remote device. π
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:
org.bluez.obex.Error.InvalidArgumentsorg.bluez.obex.Error.Failed
π object, dict PullBusinessCard(string targetfile)
Request the business card from a remote device and store it in the local file. π
If an empty target file is given, a name will be automatically generated for the temporary file. π¦
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:
org.bluez.obex.Error.InvalidArgumentsorg.bluez.obex.Error.Failed
π object, dict ExchangeBusinessCards(string clientfile, string targetfile)
Push the client's business card to the remote device and then retrieve the remote business card and store it in a local file. π
If an empty target file is given, a name will be automatically generated for the temporary file. π¦
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:
org.bluez.obex.Error.InvalidArgumentsorg.bluez.obex.Error.Failed
Signed, sealed, and very source/version-coded: BlueZ, October 2023, on the org.bluez...ObjectPush(5) manual page. ππ«Άπ
π¦ where this page comes from
- arch rolling: bluez-obex 5.87-2 Β· GPL-2.0-only
- nixpkgs unstable: bluez 5.87
- ubuntu stonking: bluez 5.87-4 Β· GPL-2.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms