diff options
| author | Barry Golden <[email protected]> | 2019-08-18 11:14:36 -0700 |
|---|---|---|
| committer | GitHub <[email protected]> | 2019-08-18 11:14:36 -0700 |
| commit | 00f43cb02d2ee88d93f73b7d6289bc30116c459a (patch) | |
| tree | 38db7c6c93edc4aa821d87993e0a3cf58a53fbc1 /bluetooth/bthecho/README.md | |
| parent | a9201e13bd23243f928c6789760eac2ccd08934f (diff) | |
* Update ReadMe.md
* Update README.md
Diffstat (limited to 'bluetooth/bthecho/README.md')
| -rw-r--r-- | bluetooth/bthecho/README.md | 12 |
1 files changed, 10 insertions, 2 deletions
diff --git a/bluetooth/bthecho/README.md b/bluetooth/bthecho/README.md index 6558f750..12cbb6e8 100644 --- a/bluetooth/bthecho/README.md +++ b/bluetooth/bthecho/README.md @@ -1,3 +1,13 @@ +--- +page_type: sample +description: "Demonstrates development of Bluetooth L2CAP profile drivers using the Bluetooth L2CAP DDIs." +languages: +- cpp +products: +- windows +- windows-wdk +--- + <!--- name: Bluetooth Echo L2CAP Profile Driver platform: WDM @@ -217,5 +227,3 @@ One transition to note here is that if disconnect is received in the connecting **Sending and receiving data from server**: When application writes data to the client, client sends this data to server on the connection opened for the given handle. Server would echo back this data. This data is retrieved by the application using a read operation. Echo Sample Client doesn't do any draining of echoed data on its own. Application read/write are handled using a parallel WDF I/O queue. **Shutdown**: Client doesn't need any specific shutdown code as connection open/close and read/write are done within the context of application's handle open. - - |