Wrox Programmer Forums
Go Back   Wrox Programmer Forums > .NET > Other .NET > .NET Web Services
|
.NET Web Services Discussions about .NET XML Web Service technologies including ASMX files, WSDL and SOAP.
Welcome to the p2p.wrox.com Forums.

You are currently viewing the .NET Web Services section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
 
Old August 21st, 2004, 10:45 AM
Registered User
 
Join Date: Aug 2004
Posts: 3
Thanks: 0
Thanked 0 Times in 0 Posts
Default Web Service Vs. Client/Server

I have a general question about when it is appropriate to use web servies instead of a traditional clinet/server setup. I am going to be writing an application where a user is going to enter various types of data into a local app. Then once a week or so they are going to send this info to the server/service. The info will be processed a little and then a report will be sent back. My question is if a web service is a reasonable way to accomplish this. From what I have read it seem like agood way to do it, but I am just wondering if there is something I am missing.

Gabe

 
Old August 22nd, 2004, 08:11 PM
Friend of Wrox
 
Join Date: Jun 2003
Posts: 1,998
Thanks: 0
Thanked 3 Times in 3 Posts
Default

Hey,

A guideline that I was told: If you plan on reaching out to multiple clients (Linux, Windows, etc.), then use Web Services; otherwise, use .NET remoting.

Brian
 
Old August 22nd, 2004, 09:35 PM
Registered User
 
Join Date: Aug 2004
Posts: 3
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Interesting I had not really heard to much about .NET Remoting before. Thw more articles I have read, the more it looks like maybe I should use Remoting instead of Web Services.

Gabe

 
Old August 23rd, 2004, 07:36 AM
Friend of Wrox
 
Join Date: Jun 2003
Posts: 1,998
Thanks: 0
Thanked 3 Times in 3 Posts
Default

Hey,

Yeah, .NET remoting is the new technology for client/server applications.

Brian
 
Old August 23rd, 2004, 08:11 AM
Registered User
 
Join Date: Aug 2004
Posts: 3
Thanks: 0
Thanked 0 Times in 0 Posts
Default

I was reading some more and a couple of things stood out to me. IT looks like one of the better reasons to use remoting is that it gives a large increase in performance. But one of the down falls is that it is a good bit more complicated to program than Web Services. Now it is not a matter of being able to figure it out, but more of a matter of how much input for a good output I can get. Performance in this case is not a huge deal, and I am going to be working on this concurrently with what I already do at work. So for me I am trying to decide if it is going to be worth me putting in the extra dev time for remoting. IT may be the case for what I need Web Services might do the trick. Does anyone have any development experience with these two technologies?

Gabe

 
Old September 5th, 2004, 11:19 PM
planoie's Avatar
Friend of Wrox
 
Join Date: Aug 2003
Posts: 5,407
Thanks: 0
Thanked 16 Times in 16 Posts
Default

The proper use of web services is really based on your "remote connectivity" needs. If your application is going to be run in a controlled environment such as a LAN/WAN where you can see the server thru a private or secure (VPN) network, then you can build a traditional client/server application in .NET that utilizes optimized technologies such as the native ADO.NET MSSQL server client. If your application needs to be run on machines that would access the data over a public network (the internet) then you should go with web services because the traditional client/server model is not acceptable due to no wanting to expose your server publicly. The web services your would expose publicly could be secure (HTTPS), require some kind of authentication and only expose what you WANT to expose, versus exposing a whole database.

Consider this aspect first, then if you are working purely internally, then you can consider the other issues mentioned.
 
Old September 7th, 2004, 09:48 AM
Friend of Wrox
 
Join Date: Jun 2003
Posts: 1,101
Thanks: 0
Thanked 2 Times in 2 Posts
Default

I'd argue that you don't want to make ADO.NET calls over the WAN- as it is usually a bottleneck.

Hal Levy
Web Developer, PDI Inc.

NOT a Wiley/Wrox Employee
 
Old September 7th, 2004, 11:10 PM
planoie's Avatar
Friend of Wrox
 
Join Date: Aug 2003
Posts: 5,407
Thanks: 0
Thanked 16 Times in 16 Posts
Default

This is true and a point well taken, however...

Which would be bulkier?
1. An optimized System.Data.SQLClient database call
2. An HTTP request

This is not to say that I'm not in favor of web services. I think that's a better way to go (more portable, easier to manager, better kewl factor). I have used it with SourceGear Vault (hosted on my home server on cablemodem) and I have seen better performance to that from my office than from a LAN based VSS.
 
Old September 8th, 2004, 10:34 AM
Friend of Wrox
 
Join Date: Jun 2003
Posts: 1,101
Thanks: 0
Thanked 2 Times in 2 Posts
Default

I think an HTTP request performs better, in my little testing I get web access requests back much faster than if I use something like Query Analyzer to talk to the SQL servers on the other side of the WAN. As a bonus, I get to spend less time talking to my Network Admin explaining why he needs to open up port x

Hal Levy
Web Developer, PDI Inc.

NOT a Wiley/Wrox Employee
 
Old September 8th, 2004, 02:15 PM
planoie's Avatar
Friend of Wrox
 
Join Date: Aug 2003
Posts: 5,407
Thanks: 0
Thanked 16 Times in 16 Posts
Default

Hmmm. I guess I should do some testing.

Not having to deal with IT about data accessibility is probably a more compelling reason to take the web service route.





Similar Threads
Thread Thread Starter Forum Replies Last Post
Calling Axis web service from .NET client Koushik .NET Web Services 4 April 2nd, 2010 09:16 PM
Web Service Server Requirements ashokparchuri .NET Web Services 0 January 2nd, 2007 06:26 PM
C# client for SOAP::Lite web service wirespring C# 0 December 8th, 2006 07:14 PM
Passing an argument to a web service from a client dotNETnewbie ASP.NET 2.0 Professional 0 April 10th, 2006 11:38 AM
Web Service Client VandanaD J2EE 0 February 13th, 2006 09:45 PM





Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.