TODO

- Bluetooth Issues
    
  * The Bluetooth discovery process have to be improved, at the moment 
  	we do discovery once and thats it. This is not good enough.
  	
  * There are two special palcom urls in bluetooth:
  	00:00:00:00:00:00: is the default multicast url and packages with this
  	address is send to all connected devices.
  	localAddress: The local address of the device is the default unicast url
  	
  * The Bluetooth implementation is build in RFCOMM since L2CAP is not 
  	supported on windows

- Add support for more than one media in one MediaManager

  * It must not be to cumbersome in the code to set up support for
    multiple media. Multiple media here, could be e.g. two 
    UDP MediaManagers, one UDP and one Bluetooth etc.

  * The current structure with managers for different media that
    extend the class MediaManager permits doing this the Composite
    design pattern way. There can be a CompoundMediaManager that
    extends MediaManager, and to which other managers can be
    added. The CompoundMediaManager handles forwarding of method calls
    to the appropriate "submanager". 

- Implement unique IDs for services

  * See discussion about naming scheme in Deliverable 15.
    
  * (The MUI implementation forms service URNs by concatenating a
    slash and a service ID to the device URN)

  * Perhaps add a class that represents the device (In
    ist.palcom.base? Or in core?) and that handles the creation of
    unique IDs for the device and its services. It is not good that
    each service has to take care of this.

- Add support for sending large messages

  * When sending large messages over e.g. UDP, they must be
    reassembled when arriving at the receiver.

  * Message losses must be handled.
