J
Jason Shohet
Lets say I have all my web services in a separate project in VS.NET. And by
referencing them in a particular web application, the dll's get
automatically put into the bin directory. I know that some people split the
web services off onto a separate box. How is this best done -- I mean, the
dll's are in the bin directory automatically. If I delete them, how is the
web application going to know to look for them on another box.
Also, if I have a server farm of 3 IIS boxes, and then create a 4th IIS box
for the web services, am I buying anything in terms of performance, since
anyways the 3 are going thru the bottleneck of 1 component server (web
services) box, in order to hit the database. I guess I'm just wondering
what the tradeoffs are, and what the best practice is.
TY
So, I create the web services as a separate project - a separate web site?
I assume I would add a 'web reference' instead of a regular reference, to
the web service, or how do I tell the application where to find it. I'm
guessing when you add reference to the web service, thats what web reference
is for?
Also doesn't this slow down your application, using a web reference vs
having the dll proxy represent the web service, right in the bin directory
of the local app. Or, (assuming the LAN is extremely fast), the
web-reference to a web service on a separate box is not really a performance
issue.
referencing them in a particular web application, the dll's get
automatically put into the bin directory. I know that some people split the
web services off onto a separate box. How is this best done -- I mean, the
dll's are in the bin directory automatically. If I delete them, how is the
web application going to know to look for them on another box.
Also, if I have a server farm of 3 IIS boxes, and then create a 4th IIS box
for the web services, am I buying anything in terms of performance, since
anyways the 3 are going thru the bottleneck of 1 component server (web
services) box, in order to hit the database. I guess I'm just wondering
what the tradeoffs are, and what the best practice is.
TY
So, I create the web services as a separate project - a separate web site?
I assume I would add a 'web reference' instead of a regular reference, to
the web service, or how do I tell the application where to find it. I'm
guessing when you add reference to the web service, thats what web reference
is for?
Also doesn't this slow down your application, using a web reference vs
having the dll proxy represent the web service, right in the bin directory
of the local app. Or, (assuming the LAN is extremely fast), the
web-reference to a web service on a separate box is not really a performance
issue.