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 / General / June 2007

Tip: Looking for answers? Try searching our database.

VB Class v WebService

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
ThatsIT.net.au - 01 Jun 2007 13:34 GMT
When I create a object I use a .net class unless I need to access it from
another web site, I just assumed that a class was a little more efficient
than a web service. But is this true?

What are the trade offs for using each?

Signature

Dim Alan as ThatsIT.net.au.Staffmember
Alan = New ThatsIT.net.au.Staffmember
Alan.signature = "Thank You"
Response.Write Alan.signature.toString()
__________________________________________

Mike - 01 Jun 2007 17:39 GMT
for the web service you need a connection to your IIS all the time. For a
class just reference the class then call the methods in that. You can still
share a class across web apps, create a class library and have your data,
business, etc classes in that then just reference the dll from your web app
or winForms apps. The difference I've noticed in using a web service is
performance due to you have to access the web service via the intranet or
internet and that can cause some issues, such as security, performance, etc.

personally I don't see a use for a web service for an internal application
unless your tranfsering data back and forth with an outside source.

> When I create a object I use a .net class unless I need to access it from
> another web site, I just assumed that a class was a little more efficient
> than a web service. But is this true?
>
> What are the trade offs for using each?
Steve C. Orr [MCSD, MVP, CSM, ASP Insider] - 02 Jun 2007 09:15 GMT
Actually web services do not necessarily need to go through IIS and HTTP.
They can be configured to use local resources in a more direct manner.
Still, there is a tiny amount of overhead so your primary point is still
valid even though it has been significantly diminished.
Some people might consider this tiny amount of overhead to be worth it in
order to have a more reusable service-oriented architecture.  But that
mostly comes down to opinion and how you envision your object model
potentially evolving over the long term.

Signature

I hope this helps,
Steve C. Orr,
MCSD, MVP, CSM, ASPInsider
http://SteveOrr.net

> for the web service you need a connection to your IIS all the time. For a
> class just reference the class then call the methods in that. You can
[quoted text clipped - 13 lines]
>>
>> What are the trade offs for using each?
Mike - 04 Jun 2007 13:20 GMT
Actually web services do not necessarily need to go through IIS and HTTP.
 interesting. How would that work? Everything I've seen, read, and even
taught in class stated a web service has run via a web server.  How can you
use or access a web service any other way?

> Actually web services do not necessarily need to go through IIS and HTTP.
> They can be configured to use local resources in a more direct manner.
[quoted text clipped - 23 lines]
>>>
>>> What are the trade offs for using each?
ThatsIT.net.au - 07 Jun 2007 17:13 GMT
> Actually web services do not necessarily need to go through IIS and HTTP.
>  interesting. How would that work? Everything I've seen, read, and even
> taught in class stated a web service has run via a web server.  How can
> you use or access a web service any other way?

I have read that they can be passed though many protocols but have never
done so.
I use web services because I always think that I may need to reuse them but
often don't and then think a class may of been the better choice.

I can consume web services in WSH excel asp pages and HTA's
can I do that with classes? If so how do I reference them?

I also remember trying to use optional parameters in a WS and they are not
allowed.

I also assume that you can not have abstract WS's

>> Actually web services do not necessarily need to go through IIS and HTTP.
>> They can be configured to use local resources in a more direct manner.
[quoted text clipped - 23 lines]
>>>>
>>>> What are the trade offs for using each?
Steve C. Orr [MCSD, MVP, CSM, ASP Insider] - 07 Jun 2007 23:23 GMT
Here's the information you requested that details how you can use protocols
other than HTTP with web services:
http://www.code-magazine.com/Article.aspx?quickid=0611051

Signature

I hope this helps,
Steve C. Orr,
MCSD, MVP, CSM, ASPInsider
http://SteveOrr.net

> Actually web services do not necessarily need to go through IIS and HTTP.
>  interesting. How would that work? Everything I've seen, read, and even
[quoted text clipped - 28 lines]
>>>>
>>>> What are the trade offs for using each?

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.