Changes between Version 14 and Version 15 of Symbian_AP_Reconnection

Timestamp:

Mar 2, 2009 4:02:16 PM (15 years ago)

Author:

bennylp

Comment:

--

Symbian_AP_Reconnection

@@ -199 +199 @@
 Note that the drawback with this approach is that it does not clean up the registration and calls properly, that is no SIP unregistration will be sent and if the application is in the middle of a call while the connection is down then no BYE will be sent either. Currently we can't suggest any other solution, as we can't get rid of the socket get stuck problem.
 
+'''Note about the socket stuck problem'''
+
 We think that this is a problem with the socket in general. Below are steps to reproduce with a plain UDP socket: 
  1. Create RConnection, call Start() to connect to AP 
@@ -209 +211 @@
 
 The problem above does not occur if: 
-- the user selects the same AP. In this case the udp.!SendTo() should complete successfully 
-- the user cancels the AP selection dialog. In this case the udp.!SendTo() will fail immediately with KErrCancel without blocking the application. 
-- the socket is closed and re-opened. In this case the udp.!SendTo() should complete successfully 
+ - the user selects the same AP. In this case the udp.!SendTo() should complete successfully 
+ - the user cancels the AP selection dialog. In this case the udp.!SendTo() will fail immediately with KErrCancel without blocking the application. 
+ - the socket is closed and re-opened. In this case the udp.!SendTo() should complete successfully 
 
 As additional info: 
-- the problem still persists even if the RConnection is restarted (RConnection.Start() is called to select new AP) in between step 3 and 4 above. 
+ - the problem still persists even if the RConnection is restarted (RConnection.Start() is called to select new AP) in between step 3 and 4 above.