El Monday 10 May 2010 04:31:22 Elvis Pfützenreuter escribió: > > > > Automatic reconnection should happen only in the case HDP has > > disconnected the transport for power-saving, because the data layer is > > idle, doesn't it? So will (b) ever happen? In the case the connection > > is dropped (loss of signal etc) the data layer should always be > > notified IMO (case c). > > MCAP spec says that > > "Because the Source and Sink assign a unique MDL ID when a new MDL is formed, using this same ID later allows a reconnection to the same context after they are intentionally closed or unintentionally broken (possibly from interference or temporarily moving out of range)." (Page 27) > > HDP spec always talks mentions "reconnection" and "power saving" near each other, but I guess it is in a broader context (not having to renegotiate every data channel after an involuntary break-up also saves power).-- Completely agree with this, reconnections should be performed until the data channel is deleted (this mdlid is no valid anymore for reconnections) or until one of the sessions is closed, the remote or the local. -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
