|
Subject:
|
Web Service Vs. Client/Server
|
|
Posted By:
|
gabrielboys
|
Post Date:
|
8/21/2004 10:45:21 AM
|
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
|
|
Reply By:
|
bmains
|
Reply Date:
|
8/22/2004 8:11:55 PM
|
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
|
|
Reply By:
|
gabrielboys
|
Reply Date:
|
8/22/2004 9:35:44 PM
|
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
|
|
Reply By:
|
bmains
|
Reply Date:
|
8/23/2004 7:36:12 AM
|
Hey,
Yeah, .NET remoting is the new technology for client/server applications.
Brian
|
|
Reply By:
|
gabrielboys
|
Reply Date:
|
8/23/2004 8:11:06 AM
|
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
|
|
Reply By:
|
planoie
|
Reply Date:
|
9/5/2004 11:19:19 PM
|
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.
|
|
Reply By:
|
Hal Levy
|
Reply Date:
|
9/7/2004 9:48:46 AM
|
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
|
|
Reply By:
|
planoie
|
Reply Date:
|
9/7/2004 11:10:01 PM
|
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.
|
|
Reply By:
|
Hal Levy
|
Reply Date:
|
9/8/2004 10:34:27 AM
|
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
|
|
Reply By:
|
planoie
|
Reply Date:
|
9/8/2004 2:15:27 PM
|
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.
|
|
Reply By:
|
andrea.wald
|
Reply Date:
|
1/10/2006 5:48:04 AM
|
hello Brian
do you have good examples to get in touch with the remoting technology?
best regards
Andrea
quote:
Originally posted by bmains
Hey,
Yeah, .NET remoting is the new technology for client/server applications.
Brian
|
