3 OBEX PUT operation.
DISCONNECT
OK, SUCCESS
Client Server
Figure 5.4 OBEX DISCONNECT operation.
Overview 91
It is important to remember that when the OBEX session has
ended, the physical connection between the two devices may not have
been closed. The transport protocol also must be disconnected. How or
when this is done is not specified by the OBEX specification.
5.2 API Capabilities
The OBEX API is quite different from most existing OBEX implementations,
which provide only a high-level interface to the protocol. For
example, Palm developers can use an API for OBEX that allows a user
to send a business card or receive an appointment but not to control how
the data was sent. Control of the specifics of the transaction is not
available. The Java OBEX API provides a low-level interface. The lowlevel
interface gives developers more control over each request and
reply, adding a new layer of complexity.
Although the OBEX API provides greater access to the protocol, the
OBEX API hides some of the details of the protocol from developers. The
OBEX API handles all the translation of OBEX headers to their corresponding
byte representation. The API also hides some of the details of
the CONNECT request. For example, the OBEX API implementation
handles the negotiation of OBEX packet sizes. Because the packet size
is not available to an application developer, the OBEX API implementation
handles converting requests into multiple packets for PUT and GET
requests.
Pages:
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133