Ask a Question related to ASP.NET Web Services, Design and Development.
-
Doug Perkes #1
handling exceptions in asynchronous web service calls
I have a win forms application that calls a web service
asynchronously. Occassionally, the web service call with raise an
exception. Unfortunately, since I am calling it asynchronously, I
haven't been able to find a good way to handle exceptions.
Can anyone point me in the right direction?
Thanks,
Doug
Doug Perkes Guest
-
Asynchronous calls from Java?
Hi, I want to listen for events on the java side and have a flex method called when something happens. How would I do this? This should be... -
Web service calls asynchronous vs synchronous
The best solution is to design you architecture using the observer pattern(GOF) K,Browne Developer -
Asynchronous web service calls
Hi I am trying to do some tests using asynchronous web service calls and have hit a problem. I have reduced the problem to the minimum so... -
Asynchronous web service calls, will you still have timeouts
If I am calling web services asynchronously, will I still have to be concerned with the request timing out? If IIS starts a process (calling a web... -
Blocking problem/bug with enableSession=true and asynchronous web service calls?
Hi, I've found what appears to be a bug with ASP.NET web service method invocation - making it impossible to invoke and get the result of a... -
Jeffrey Hasan #2
Re: handling exceptions in asynchronous web service calls
Is the nature of your question more design-oriented? Meaning, are you asking
how to gracefully handle asynchronous errors once the user is already doing
something else in the WinForms app? Depending on the nature of the
information, you may want to switch the Web service call to be synchronous
rather than asynchronous. Alternatively, there is a hybrid broker/service
agent approach, whereby you make a synchronous call to a broker, which in
turn makes asynchronous calls to a number of web services and aggregates the
results. You are limited to waiting for the longest running Web service
operation, but at least the results are returned to you all at once by the
broker.
If you are looking to make single asynchronous calls, then exception
handling will always be problematic, because you cannot control the timing
of a return error with a coordinated response, since it's not clear what the
application user will be doing when the error returns. My recommendation is
to go synchronous, or, if it is possible, aggregate your asynchronous Web
service calls with a synchronously called broker.
Jeffrey Hasan, MCSD
President, Bluestone Partners, Inc.
-----------------------------------------------
Author of: Expert SOA in C# Using WSE 2.0 (APress, 2004)
[url]http://www.bluestonepartners.com/soa.aspx[/url]
"Doug Perkes" <dougperkes@gmail.com> wrote in message
news:10f816a.0408060800.6b44dd42@posting.google.co m...> I have a win forms application that calls a web service
> asynchronously. Occassionally, the web service call with raise an
> exception. Unfortunately, since I am calling it asynchronously, I
> haven't been able to find a good way to handle exceptions.
>
> Can anyone point me in the right direction?
>
> Thanks,
>
> Doug
Jeffrey Hasan Guest



Reply With Quote

