Remove L2CAP LE CoC related document 77/299577/1 accepted/tizen_6.0_unified tizen_6.0 accepted/tizen/6.0/unified/20231010.005233
authorWootak Jung <wootak.jung@samsung.com>
Thu, 5 Oct 2023 07:41:57 +0000 (16:41 +0900)
committerWootak Jung <wootak.jung@samsung.com>
Thu, 5 Oct 2023 07:41:57 +0000 (16:41 +0900)
Change-Id: I8ce6d29409a4b38d744cd8dfc8e4fb7d432caf40
Signed-off-by: Wootak Jung <wootak.jung@samsung.com>
doc/bluetooth_doc.h

index 30d039c44abad86da9f88910a86fd1c969321871..3d333c368d1426b934c20eaf6ab26e0aa22d301c 100644 (file)
  * Please refer Bluetooth Tutorial if you want to get more detailed usages and information of this api.
  */
 
-/**
- * @defgroup CAPI_NETWORK_BLUETOOTH_L2CAP_SOCKET_MODULE Bluetooth L2CAP Socket
- * @brief Bluetooth L2CAP Socket API provides functions for managing connections to other devices and exchanging data.
- * @ingroup CAPI_NETWORK_BLUETOOTH_MODULE
- *
- * @section CAPI_NETWORK_BLUETOOTH_L2CAP_SOCKET_MODULE_HEADER Required Header
- *  \#include <bluetooth.h>
- *
- * @section CAPI_NETWORK_BLUETOOTH_L2CAP_SOCKET_MODULE_OVERVIEW Overview
- * This set of functions is used for exchanging data between two bluetooth
- * devices, our device can have both roles as server (service provider) and client
- * (service user).
- * Depending on the role, there is difference in creating a connection.
- * After that, processes of exchanging data and disconnection are same.
- *
- * To start communication, you should first register for #bt_socket_set_l2cap_channel_connection_state_changed_cb()
- * and #bt_socket_set_data_received_cb().
- * Next step depends on the role of your application.\n
- * If you want to be \b server \b role, application should create socket
- * (#bt_socket_create_l2cap_channel()), and start listening and accepting incoming connections
- * (#bt_socket_listen_and_accept_l2cap_channel()).
- * If you want to connect to specific device and use it's services (\a client \a role),
- * you have to start connection with #bt_socket_connect_l2cap_channel() and wait for connection.\n
- * After connection has been established (information is passed to your program with
- * #bt_socket_l2cap_channel_connection_state_changed_cb() function call), you can exchange data by
- * calling #bt_socket_send_data_l2cap_channel(). \n
- * If you receive data from remote device, #bt_socket_data_received_cb() functions will be called.
- * When you finish exchanging data, you should disconnect connection
- * with #bt_socket_disconnect_l2cap_channel() and unregister callback functions (with using
- * #bt_socket_unset_data_received_cb(), #bt_socket_unset_l2cap_channel_connection_state_changed_cb()).
- *
- * @section CAPI_NETWORK_BLUETOOTH_L2CAP_SOCKET_MODULE_FEATURE Related Features
- * This API is related with the following features:\n
- *  - %http://tizen.org/feature/network.bluetooth.le.coc\n
- *
- * It is recommended to design feature related codes in your application for reliability.\n
- *
- * You can check if a device supports the related features for this API by using @ref CAPI_SYSTEM_SYSTEM_INFO_MODULE,thereby controlling the procedure of your application.\n
- *
- * To ensure your application is only running on the device with specific features, please define the features in your manifest file using the manifest editor in the SDK.\n
- *
- * More details on featuring your application can be found from <a href="https://docs.tizen.org/application/tizen-studio/native-tools/manifest-text-editor#feature-element"><b>Feature Element</b>.</a>
- *
- * @section CAPI_NETWORK_BLUETOOTH_L2CAP_SOCKET_MODULE_ASYNCHRONOUS_OPERATIONS Asynchronous Operations
- * <div><table class="doxtable" >
- *     <tr>
- *        <th><b>FUNCTION</b></th>
- *        <th><b>CALLBACK</b></th>
- *        <th><b>DESCRIPTION</b></th>
- *     </tr>
- *     <tr>
- *        <td>bt_socket_listen_and_accept_l2cap_channel()<br>
- *            bt_socket_connect_l2cap_channel()</td>
- *        <td>bt_socket_l2cap_channel_connection_state_changed_cb()</td>
- *        <td>Used to connect a device. </td>
- *     </tr>
- *</table></div>
- *
- * @section CAPI_NETWORK_BLUETOOTH_L2CAP_SOCKET_MODULE_CALLBACK_OPERATIONS Callback(Event) Operations
- * <div><table class="doxtable" >
- *     <tr>
- *        <th><b>REGISTER</b></th>
- *        <th><b>UNREGISTER</b></th>
- *        <th><b>CALLBACK</b></th>
- *        <th><b>DESCRIPTION</b></th>
- *     </tr>
- *     <tr>
- *        <td>bt_socket_set_data_received_cb()</td>
- *        <td>bt_socket_unset_data_received_cb()</td>
- *        <td>bt_socket_data_received_cb()</td>
- *        <td>Used to be notified of received data. </td>
- *     </tr>
- *     <tr>
- *        <td>bt_socket_set_l2cap_channel_connection_state_changed_cb()</td>
- *        <td>bt_socket_unset_l2cap_channel_connection_state_changed_cb()</td>
- *        <td>bt_socket_l2cap_channel_connection_state_changed_cb()</td>
- *        <td>Used to be notified when the state of connection changes. </td>
- *     </tr>
- *</table></div>
- *
- *<BR>
- * Please refer Bluetooth Tutorial if you want to get more detailed usages and information of this api.
- */
-
 /**
  * @defgroup CAPI_NETWORK_BLUETOOTH_OPP_MODULE Bluetooth OPP
  * @brief Bluetooth OPP(Object Push Profile) API provides functions for exchanging objects such as pictures.