/* new todo file for BTstack */

2009-11-08: Release 0.1

NEXT:
- clean up control flow
  - l2cap directly sends data over socket: good/bad?
  - split daemon into stack parts
  - should there be STACK API/interface?
- BUG: bt_close crashes when used in CocoaTouch app
- add extern "C" to bstack methods
  - see: http://stackoverflow.com/questions/376966/using-c-c-static-libraries-from-iphone-objectivec-apps
- Provide BTstackManager Objective-C class
  - move connection methods to BTdevice (get more object oriented)
    - initWithAddress:(bd_addr_t *)addr
	- setters private
  - implement l2cap code
  - implement rfcomm code
- figure out how to receive iPhone System Power IONotifications (in BTdaemon) to detect, when phone gets locked
  - some trick
  - use Cocoa run loop for background app?
- move RFCOMM code into BTdaemon
- add timeouts to cocoa run loop
- L2CAP 
  - segmentation

== Release 0.2 - Incoming L2CAP supported + improved Inq Dialog
- extend SpringBoard feedback
  - show alerts/messages using SpringBoardAcccess, e.g. Bluetooth disconnected by remote device
  - add code to notify about remote disconnets
- configuration: /etc/btstack
  - single Bluetooth module supported
  - transport type: H4, H5, USB
  - h4/h5: UART path
  - usb: product/vendor ID
  - logging mode: text, bluez, packetlogger
- implement rest of L2CAP state machine
  - error handling
  - error notification
  - flow control
- add configure option for uart flowcontrol
- create <btstack/errors.h>

== Release Version 0.3
- implement RFCOMM server
- implement SDP
- implement PAN

== Release Version 0.4
- unify packet generation
  - btstack events
  - cmd packets
  - l2cap commands
- auto-generate code for sending commands from structured text input file
- devise concept for access to event data
  - auto-generate event struct getter? STRUCTURE_get_FIELD
- Bluetooth low-power modes useful

== USB Support ==
- Store array of data sources to be able to remove them on usb_close