Top | ![]() |
![]() |
![]() |
![]() |
BtctlObex * | btctl_obex_new () |
gboolean | btctl_obex_is_initialised () |
void | btctl_obex_set_response () |
void | btctl_obex_cancel_operation () |
void | btctl_obex_cancel_operation_forcibly () |
void | complete | Run First |
void | connect | Run First |
void | disconnect | Run First |
void | error | Run First |
void | progress | Run First |
void | put | Run First |
void | request-put | Run First |
struct | BtctlObex |
#define | BTCTL_OBEX_ERR_PARSE |
#define | BTCTL_OBEX_ERR_LINK |
#define | BTCTL_OBEX_ERR_ABORT |
BtctlObex *
btctl_obex_new (void
);
Create a new Bluetooth OBEX object. This will attempt to open
an OBEX server socket. Use btctl_obex_is_initialised()
to check
whether this was successful.
gboolean
btctl_obex_is_initialised (BtctlObex *bo
);
Check if OBEX was able to initialise OK. If not, we won't be able to do anything.
void btctl_obex_set_response (BtctlObex *bo
,gboolean resp
);
Sets TRUE or FALSE response in signal handlers that must decide whether an operation can proceed or not.
void
btctl_obex_cancel_operation (BtctlObex *bo
);
Requests the cancel of a currently running transfer, disconnecting the client.
void
btctl_obex_cancel_operation_forcibly (BtctlObex *bo
);
Forcibly causes the closing of a client connection. Use if the client isn't responding to a cancel request, e.g. where the connection's timing out.
#define BTCTL_OBEX_ERR_PARSE 0x01
A parse error has occured on incoming packets. Usually this happens when the connection is aborted.
“complete”
signalvoid user_function (BtctlObex *btctlobex, gchar *arg1, gpointer user_data)
bo |
the object which received the signal. |
|
bdaddr |
the remote address of the requestor. |
|
user_data |
user data set when the signal handler was connected. |
Flags: Run First
“connect”
signalvoid user_function (BtctlObex *btctlobex, gchar *arg1, gpointer user_data)
btctlobex |
the object which received the signal. |
|
user_data |
user data set when the signal handler was connected. |
Flags: Run First
“disconnect”
signalvoid user_function (BtctlObex *btctlobex, gchar *arg1, gpointer user_data)
btctlobex |
the object which received the signal. |
|
user_data |
user data set when the signal handler was connected. |
Flags: Run First
“error”
signalvoid user_function (BtctlObex *btctlobex, gchar *arg1, guint arg2, gpointer user_data)
bo |
the object which received the signal. |
|
bdaddr |
the remote address of the requestor. |
|
reason |
the error code of the signal. |
|
user_data |
user data set when the signal handler was connected. |
Flags: Run First
“progress”
signalvoid user_function (BtctlObex *btctlobex, gchar *arg1, gpointer user_data)
bo |
the object which received the signal. |
|
bdaddr |
the remote address of the requestor. |
|
user_data |
user data set when the signal handler was connected. |
Flags: Run First
“put”
signalvoid user_function (BtctlObex *btctlobex, gchar *arg1, gchar *arg2, BtctlObexData *arg3, guint arg4, gpointer user_data)
Emitted when a remote peer has completed transmission
of an OBEX PUT. Use btctl_obex_set_response()
to indicate
whether you accepted or denied the PUT.
bo |
the object which received the signal. |
|
bdaddr |
the remote address of the requestor. |
|
fname |
the suggested filename of the transferred object. |
|
body |
the data of the object. |
|
len |
the length in bytes of the data. |
|
user_data |
user data set when the signal handler was connected. |
Flags: Run First
“request-put”
signalvoid user_function (BtctlObex *btctlobex, gchar *arg1, gpointer user_data)
Emitted when a peer hints it is about to PUT.
Use btctl_obex_set_response()
to indicate
whether you want the PUT to continue or not. For small
payloads, the PUT will still happen regardless, so
you should be prepared to deny it when receiving the
"put" signal. For larger
payloads, the connection will be aborted and dropped.
btctlobex |
the object which received the signal. |
|
bdaddr |
the remote address of the requestor. |
|
user_data |
user data set when the signal handler was connected. |
Flags: Run First