What is OBEX ?
OBEX refers to Object Exchange, which is a protocol for exchange of communications, which helps the exchanging of binary objects from one device to another.
Administered by the Infrared Data Association, a subsidiary of the Bluetooth Special Interest Group as well as SyncML, which is part of the OMA or Open Mobile Alliance, OBEX, came out in very early stages with its PDA application known as Palm II digital assistant, which has been used along with many such devices, exchanging business identity cards, applications and data.
Though primarily intended for infrared transmission, OBEX has been adopted by Bluetooth, while even Livescribe pens and other technologies such as WAP (Wireless Application Protocol), RS-232, USB also make use of this. In more than one way, OBEX resembles HTTP in giving users a reliable way to connect servers and request them for providing objects.
It however differs from HTTP, in a number of ways. First of all, HTTP layers itself over TCP/IP links in protocol stacks. OBEX, however commonly is usually executed on IrLAP/Tiny TP/IrLMP stack on IrtDA apparatus. OBEX is executed on Bluetooth on a Baseband/ACL/L2CAP/RFCOMM Stack. Similar bindings like that on USB are also adopted for OBEX.
While HTTP makes use of ordinary human read text, OBEX makes use of binary formats called “headers” for exchange of objects or textual information, simply due to the reason that they are easily parsed by devices that have limited resources.
Business carried out on HTTP are intrinsically stateless; usually a client using HTTP unlocks a connection, proceeds to make only one request and when a response is received, and they are now left with option of closing HTTP, or to proceeds with other requests which that are not related to HTTP.
Compared with OBEX, which has a single connection of transport, possibly having many related nuances and operations. In some recent advancement to specifications of OBEX, allow an unexpectedly closed transaction to be resuscitated with all the details intact.