Hi Patrik On 21.10.2011 14:34, Patrik Flykt wrote: > On Thu, 2011-10-13 at 08:04 -0700, Daniel Wagner wrote: >> +When the application calls Disconnect() the session enters the >> +Disconnect state and stays there until the application calls Connect() >> +again. >> + >> + >> + State Change to offline & StayConnected = True >> + +------+ >> + | v >> ++-----------+ +---------+ +------------+ >> +| Free Ride |-- Connect() -->| Connect |-- Disconnect() --> | Disconnect | >> ++-----------+ +---------+ +------------+ >> + | ^ | ^ >> + | +------------------------ + | >> + | State Change to offline & StayConnected = False | >> + | | >> + | | >> + +----------------------- Disconnect() -----------------------+ > > In state Disconnect, I assume the session goes to state Connect when > Connect() is called (that arrow is missing in the picture).
Good catch. I have added it now. > How does a > session in Free Ride get back to Free Ride if it has called > Disconnect()? Currently the only way is to call Connect() with StayConnected = False. I am not really happy with this either. Also it might be necessary to start in the Disconnect state instead of the Free-Ride. Or maybe we should always start in Disconnect and have some way to go directly to free ride. Fiddling with StayConnected is kind of difficult to understand. This documents the current behavior. I'll add this info to the document. Though I agree we should fix this. cheers, daniel _______________________________________________ connman mailing list [email protected] http://lists.connman.net/listinfo/connman
