Editing OBject EXchange (section)

==Session==

After the client (e.g., computer) connects to the server (e.g., mobile), a typical session consists in the client sending a number of objects and getting their responses from the server. As an example:

* CONNECT: one of the fields specifies the largest size of packets the client can receive; a TARGET header specifies the kind of service the client is expecting (file-browsing, sync-ml, phonebook access); the server answer with its maximal packet length, the connection id, and other data
* GET: the client requests a file, specifying the connection id, the file name and/or its type; the server answer with the file content, or just a part of it; in the latter case, the client has to send other GET objects to obtain the rest of the file
* SETPATH: the client tells the server to switch to a different file folder, specifying the connection id and the folder name in two headers
* GET: the client requests a listing of the folder content by sending an object with the connection id and an appropriate TYPE header (e.g., "x-obex/folder-listing" for file transfer, "x-bt/vcard-listing" for phonebook access)
* PUT: the client sends a file to the server; if it is too large to fit into a single packet, the server will request the next part with a CONTINUE response
* DISCONNECT: the client informs the server that it is closing the session

The exchange may differ significantly depending on the service. For example, [[SyncML]] does not use SETPATH, while an [[OBEX push]] is made of just CONNECT (without a TARGET header), PUT and an optional DISCONNECT.