Can TU check for an active/available TCP/IP connection and then immediately shutoff is one is not available? Or is it limited to waiting for the duration of the connection timeout?
The reason I ask is this: I have been using TU successfully in my ASP based product for over a year and am quite happy with it. Recently, however, we have come across a weird phenomenon. When certain users are not connected to the Net the Client just sits there and does not allow the user to click on to another page in the app until the timeout is reached and the client goes away. It is very odd.
I do not display a dialog of any kind unless an update is actually available do to the "experience level" of my users. :
Thanks!
The reason I ask is this: I have been using TU successfully in my ASP based product for over a year and am quite happy with it. Recently, however, we have come across a weird phenomenon. When certain users are not connected to the Net the Client just sits there and does not allow the user to click on to another page in the app until the timeout is reached and the client goes away. It is very odd.
I do not display a dialog of any kind unless an update is actually available do to the "experience level" of my users. :
Thanks!
Comment