Webservice vs dll from Classic ASP

[mpaturi]

Should I use a webservice or a class library for some processing that will be called from classic asp.
What are the pros and cons of each.

[CroCrew]

How about you list off what you want/trying to do; then we could give you a list of Pros/Cons. Really; a general answer is not always the correct answer to a solution. Letting us know your enviroment would get you a correct answer for your solution.

CroCrew~

[mpaturi]

I am trying to pass variables from asp pages to this application that will in turn form an XML request that will be passed to another third party application which will send an appropriate response for the request. Information passed is financial and the application should use multiple threads.

I am interested in finding out the overhead that will be involved in making the webservice calls vs the dll.

[jhardman]

I am trying to pass variables from asp pages to this application that will in turn form an XML request that will be passed to another third party application which will send an appropriate response for the request. Information passed is financial and the application should use multiple threads.

I am interested in finding out the overhead that will be involved in making the webservice calls vs the dll.

I like web services because they run completely independent of the web app (asp in this case).

If you are running a .NET web service, it will be compiled and run separately from the web app. The communication causes a brief lag, but if the service takes a while to run it will run faster like this.

If you use a dll ASP will run it as a server object. This will make the server run slower in the long run, so I wouldn't use that if the calculations it performs are especially long or if it takes a lot of memory. but if it is a fairly simple calculation, that would be faster because you don't have to wait to communicate with a web service.

Jared