6.3.1. Forklistener

This is a standard program reading data from standard input and writing output to standard output. See SDK's directory examples/forkserver/ for an example of this kind of program.

Pros:

• Easy to write.

• Very robust for simple services.

• You don't have to know anything about Bluetooth or iWRAP.

Cons:

• Your program is started and stopped for every incoming connection.

• If there are multiple connections it is not possible to communicate to external program via one socket.

• You can't use stdout for debugging, you have to use syslog or a log file.

• iWRAP's advanced features are not available: powermodes, MSC, SDP, inquiry, ...

To setup a forklistener see SET command.

6.3.2. iWRAP Client

iWRAP client is a program communicating with the iWRAP server via control and data sockets. See SDK's directory examples/btserver/ for an example of this kind of program.

Pros:

• The cons with forklistener do not apply.

Cons:

• More complex than forklistener.

• You must have basic knowledge about Bluetooth and iWRAP.

For documentation about iWRAP read this chapter carefully.

6.10.1. libobex

Initialize the OBEX library. Must be the first function called. s_in and s_out are data handles for reading and writing.

Deinitialize the OBEX library. Must be the last function called.

Receive one OBEX packet. You have to free() the received packet! If NULL is returned, you have to disconnect next (timeout, dead socket, ...). If timeout is zero, wait forever. If timeout is nonzero, wait up to timeout seconds.

Send one packet. Does not call free().

Initialize an OBEX packet to empty command type packet.

Add byte/long/unicode-string/binary/ascii data to an OBEX packet.

Find header data from an OBEX packet. Returns -1 if not found, otherwise the length of the data.

Return mime type for filename.

6.10.2. libobexclient

Connect to target UUID. Target can be NULL (Object Push connect). Returns 0 if no errors, -1 if timeout, -2 if broken socket, >0 if OBEX error (see IrDA Object Exchange Protocol by Infrared Data Association for OBEX response codes).

Disconnect. Returns 0 if no errors, -1 if timeout, -2 if broken socket, >0 if OBEX error (see IrDA Object Exchange Protocol by Infrared Data Association for OBEX response codes).

Put local file / data block to remote.

name is remote file name. Can be NULL.

type is remote MIME type. Can be NULL.

data/length are pointer to data block and length. Can be NULL/0.

fdata is file handle for local file, if data was NULL.

progress is a function to be called after each data block. Can be NULL. progressarg will be passed as parameter.

Returns 0 if no errors, -1 if timeout, -2 if broken socket, >0 the OBEX error code (see IrDA Object Exchange Protocol by Infrared Data Association for OBEX response codes).

Get remote file to local.

name is remote file name. Can be NULL.

type remote MIME type. Can be NULL.

data/max_length are pointer to data block and length. Can be NULL/0.

fdata is file handle for local file, if data was NULL.

progress is a function to be called after each data block. Can be NULL. progressarg will be passed as parameter.

Returns >=0 (number of bytes received) if no errors, -1 if timeout, -2 if broken socket, <0 if OBEX error (see IrDA Object Exchange Protocol by Infrared Data Association for OBEX response codes).

Setpath to name with flags. Returns 0 if no errors, -1 if timeout, -2 if broken socket, >0 if OBEX error (see IrDA Object Exchange Protocol by Infrared Data Association for OBEX response codes).

6.10.3. obexbrowser

The application obexbrowser is an Object Push Profile (ObjP) and File Transfer Profile (FTP) client, and is shipped with Access Server in both binary form (as it is part of the Access Server platform) and in source form (at it is a good example of using the OBEX libraries).

For an outgoing ObjP/FTP call you need to:

1. Make the outgoing RFCOMM call from iWRAP.

   For example: CALL 00:07:80:80:bf:01 FTP RFCOMM

2. Run obexbrowser from the command line. It takes two parameters: hostname and port number. Hostname is usually localhost and port number can be read from the iWRAP server's CONNECT reply.

   For example: obexbrowser localhost 1024

obexbrowser itself supports all the OBEX commands. See the source code and the IrDA Object Exchange Protocol by Infrared Data Association. The commands obexbrowser accepts are described in Table 6-11.

Example:

          iWRAP server:
          READY.
          CALL 00:07:80:80:bf:01 3 RFCOMM
          CALL 0
          RINGING 0
          CONNECT 0 RFCOMM 1024
          Command line:
          obexbrowser localhost 1024
          connect
          connect=00
          get remote.vcf -
          get=143
          put default.vcf
          put=00
          disconnect
          disconnect=00
          Ctrl-D
          iWARP server:
          NO CARRIER 0 ERROR 000