Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / ASP.NET / Web Services / October 2005

Tip: Looking for answers? Try searching our database.

Multithreading and Async Web Service processing

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Simon Hart - 24 Oct 2005 10:40 GMT
Hi,

I thought I'd just open a thread in an attempt to get peoples feelers with
regards to multithreading vs Async Web Service processing.

Of course Web Services makes it easy to do Async method calling, but what if
you are already in a worker thread in a Windows Forms application when doing
the web service call. In this case there is no need to use Async Begin..End
features that .NET kindly presents us with.

Is there any extra gain in using an existing worker thread to do Web Service
method calls features over the built in Begin..End ? or is it more effecient
to use the Web Service Async features?

Regards
Simon.
John Scragg - 24 Oct 2005 20:42 GMT
I got one positive and one negative to Async service calls versus a new
thread.  

Positive: Asnyc calls allow you to "cancel" a web service call.  Granted it
does not save the server from doing the work, but at least it gives you a
means to interact from the UI.  For instance, if you are calling a webmethod
that performs a lengthy search, but want to cancel it.... Async makes that
nice and clean on the client side (just make sure to handle the web exception
in the callback method :P

Negative.  Overloading.  I like to use overloaded methods becuase it makes
my intellisense nice and neat :)  WebServices accomidate this by letting you
assign a MessageName attribute to the method so that for the service it has a
unique name, but your proxy will overload it ias normal.  The downside to
this is that for Begin .. End methods that get created are just numbered.  
BeginSearch1, BeginSearch2, etc.   That just plain sucks, and I can only
assume it will "renumber" them if you add new methods.  I am not even sure
what logic it uses to get the numbers :)

Anyway, interesting topic.

John

> Hi,
>
[quoted text clipped - 12 lines]
> Regards
> Simon.

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.