|
-
Jun 17th, 2005, 02:44 PM
#1
Thread Starter
Hyperactive Member
Web Service Vs. Normal Component.
Hi,
I am kinda confused exactly when to use WebService and When to use Normal Component ?? You can almost always make all Business Components as a WebService whether needed or not. So is there a drawback in doing so ?? I mean do we lose some performance or something in making a Component (which can be a normal component) a Web Service ?? Or the other way around ??
-
Jun 18th, 2005, 06:56 AM
#2
Re: Web Service Vs. Normal Component.
Generally speaking, web services have an associated performace penalty. But they offer easy interoperability with third-party systems and frameworks other than .Net.
-
Jun 18th, 2005, 09:39 AM
#3
Re: Web Service Vs. Normal Component.
What's nice about using web services is, you can access all your components through one reference. Also, it makes migrating new changes to the components alot easier, as you can make changes to the production components the web service calls.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|