Asynchronous call problem

[strout]

I am using ASP.net as web service client.

I call BeginInvoke in a proxy and use a callback function to process the
result.

However, the callback function is not the same thread of the web page. I end
up doing nothing, even though the callback function( updating the web page )
is called.

I found lots of example use windows form raise event. When I try to create
delegate and fire event in ASP page. It doesn't work because the response is
already sent to browser and there is no way you can change anything on that
page. I am not sure if I am on the right track. This must be a very common
problem in web service/ASP.net.

strout

[Loek]

What you could do is to have a polling mechanism on your ASP.NET page to see
if the webservice reply has already been delivered. All you need is a store
for replies, and associate a reply with a request you send to the WS by using
GUID's. This is a very scalable solution.
Another option would be to use the WebService htc (HTML component), which
works client-side.

"strout" wrote:

I am using ASP.net as web service client.

I call BeginInvoke in a proxy and use a callback function to process the
result.

However, the callback function is not the same thread of the web page. I end
up doing nothing, even though the callback function( updating the web page )
is called.

I found lots of example use windows form raise event. When I try to create
delegate and fire event in ASP page. It doesn't work because the response is
already sent to browser and there is no way you can change anything on that
page. I am not sure if I am on the right track. This must be a very common
problem in web service/ASP.net.

strout