Discussion:
Problem with synchronous server call
(too old to reply)
Christian Havel
2005-11-28 15:11:07 UTC
Permalink
Hi,

I make a call from my VB6 Microsoft Project AddIn to a remote XML-RPC-Server.
Sometimes the server has some problems and hangs. In this case my app hangs
too, because I am waiting on the response from the server.

I want to create a timer, and if a specified time is expired the user should
be informed about this problem.

How can I solve this problem?

Thanks from Munich
Christian
Sinna
2005-11-29 07:07:24 UTC
Permalink
Post by Christian Havel
Hi,
I make a call from my VB6 Microsoft Project AddIn to a remote XML-RPC-Server.
Sometimes the server has some problems and hangs. In this case my app hangs
too, because I am waiting on the response from the server.
I want to create a timer, and if a specified time is expired the user should
be informed about this problem.
How can I solve this problem?
Thanks from Munich
Christian
To solve issues like this, I create an ActiveX EXE functioning as a
proxy for the application. In that proxy I implement a mechanism to
allow 'asynchronous' calls. To accomplish this I launch a timer with the
smallest interval possible and when it fires, the synchronous call is
performed. In the meanwhile another timer is set to check for the
timeout. The first one that fires (the timer or the synchronous call) is
raised as event (or using callbacks) to the application. When the other
returns, a flag is set not to inform the application (has been done
before!).


Sinna
Christian Havel
2005-11-29 07:56:03 UTC
Permalink
Hi Sinna,

thanks for your help!

I will try the way you describe.

Bye from Munich

Christian
Post by Sinna
Post by Christian Havel
Hi,
I make a call from my VB6 Microsoft Project AddIn to a remote XML-RPC-Server.
Sometimes the server has some problems and hangs. In this case my app hangs
too, because I am waiting on the response from the server.
I want to create a timer, and if a specified time is expired the user should
be informed about this problem.
How can I solve this problem?
Thanks from Munich
Christian
To solve issues like this, I create an ActiveX EXE functioning as a
proxy for the application. In that proxy I implement a mechanism to
allow 'asynchronous' calls. To accomplish this I launch a timer with the
smallest interval possible and when it fires, the synchronous call is
performed. In the meanwhile another timer is set to check for the
timeout. The first one that fires (the timer or the synchronous call) is
raised as event (or using callbacks) to the application. When the other
returns, a flag is set not to inform the application (has been done
before!).
Sinna
Loading...