3

The project im working on, they would like active server connection detection before each call.

Im trying to find out if its better to use: WL.Device.getNetworkInfo:isNetworkConnected or WL.Client.connect

I know that getNetworkInfo only checks if the phone has contectivity to the net, while wl.client.connect will actually connect to the server. Im just afraid that wl.client.connect will be an expensive call to make before every invokeProcedure call. Is there a better way to check for connectivity before the invokeProcedure call?

tik27
  • 2,698
  • 1
  • 16
  • 25

1 Answers1

4

getNetworkInfo API can be used to verify whether device currently has an internet connectivity.

As for WL server connectivity there is only one way to verify that server is accessible and this is by issuing a request to WL server and verifying whether it succeeded. However this is not right way to go. Every WL server invocation API, e.g. WL.Client.connect(), WL.Client.login(), WL.Client.invokeProcedure(), has onSuccess and onFailure callbacks. Use them to verify whether server connectivity was successful or not.

Technically, even if you do additional request like WL.Client.connect() before making a real request it will not give you 100% assurance that the real request will succeed.

In addition you may want to utilize WORKLIGHT_IS_CONNECTED and WORKLIGHT_IS_DISCONNECTED events which are fired each time last WL server invocation status toggles success<->failure. Check out the offline training module at Worklight Getting Started page.

Anton
  • 3,166
  • 1
  • 13
  • 12