org.bluez.obex.Agent(5)

okay so bestie, this is the manual page for org.bluez.obex.Agent(5) β€” the BlueZ D-Bus OBEX Agent API doc. no cap, it’s giving β€œtiny interface, big main-character energy” ✨

πŸŽ€ NAME πŸŽ€

org.bluez.obex.Agent β€” BlueZ D-Bus OBEX Agent API documentation πŸ’–

πŸ’… INTERFACE πŸ’…

here’s the vibe check for the D-Bus interface, bestie:

  • Service β€” unique name
  • Interface β€” org.bluez.obex.Agent1
  • Object path β€” freely definable

✨ METHODS ✨

🌸 void Release()

this method gets called when the obexd(8) daemon unregisters the agent. πŸ‘‘

an agent can use it to do cleanup tasks. there is no need to unregister the agent, because when this method gets called it has already been unregistered. periodt.

πŸ¦‹ string AuthorizePush(object transfer)

this method gets called when the obexd(8) needs to accept/reject a Bluetooth object push request. yes, accept or reject β€” it’s literally the vibe check for incoming pushes πŸ’…

it returns the full path (including the filename) or the folder name suffixed with '/' where the object shall be stored.

the transfer object, see org.bluez.obex.Transfer(5), will contain a Filename property that contains the default location and name that can be returned. πŸŽ€

possible errors:

  • org.bluez.obex.Error.Rejected
  • org.bluez.obex.Error.Canceled

πŸ”₯ void Cancel()

this method gets called to indicate that the agent request failed before a reply was returned. it cancels the previous request. no cap, it’s the cleanup-on-failure button. 😭


πŸ’– okay that’s the whole page, bestie! this is from BlueZ, dated October 2023, and the manual is literally org.bluez.obex.Agent(5) β€” periodt. πŸŽ€βœ¨

πŸ“¦ where this page comes from