Symbian signed criteria regarding Connections???

[gmsk19]

Hi All,

I am using Connections in my application. I came across certain symbian signed criteria w.r.t to connections. I only have a vague idea abt these criteria . Can any one clarify the actual end result that needs to happen. My application actually passes the tests in this regard but i just wanted to be sure abt what these actually mean.

• If the application creates connections start a connection and close it from the connection manager before the connection is fully established..

• If the application uses connections. Use the connection manager to close the connection suddenly.

Is it necessary for me to disconnect when connection manager Closes the connection??? or can i continue

[ltomuta]

Since the connection is closed by the user through the Connection Manager then you are in fact disconnected and you application should of course reflect that status.

E.g. if the application has a Connect menu option which then changes into a Disconnect once the connection is established should, upon external disconnect, revert to the disconnect state and offer the Connect option to the user.
Any other status information should reflect the offline state.

[gmsk19]

what if the User deletes the Connection in use when the AO is Idle?? should i disconnect then??

[amitkankani]

i guess when the connection in use is deleted, you are automatically disconnected, however, you have to handle the case by prompting aptly to the user and either closing the app, or letting the user choose the new connection he prefers..

i hope i got your query right !

[ltomuta]

Exactly, there's nothing to actively disconnect since there is no connection anymore. You just need to be aware of the status and update the UI.

In practice in your code you my have to perform some cleanup operations similar to a disconnect but that pretty much depends on your application's design.

[gmsk19]

Thanks amit and ltomuta for your very precise answers,yes amit you definately got my query right. i am now handling this case as required by my application's design.