Chapter 5 – OBEX
暂无分享,去创建一个
Publisher Summary
This chapter deals with OBEX that provides a structured way to send data between embedded devices. OBEX was defined by IrDA and adopted by the Bluetooth SIG. The Generic Object Exchange Profile (GOEP) defines OBEX within the Bluetooth world. Many different profiles are defined on top of GOEP. For Bluetooth devices, OBEX uses the RFCOMM protocol as the transport protocol. OBEX is built on a request and response scheme. The client drives the connection by issuing requests to the server. The server can accept or reject the request using any of the HTTP response codes. CONNECT, PUT, GET, SETPATH, DELETE, CREATE EMPTY, and DISCONNECT are the valid operations that may be performed by a client. A client session begins with a CONNECT request and ends with a DISCONNECT request. OBEX also provides a mechanism for authentication. This method is different from Bluetooth authentication. OBEX authentication uses a challenge and response scheme.