Hi all,
I've developed a web service in C# with VS.NET, and am planning on setting up some additional web methods that make calls to other web methods. Obviously, if I declare these web methods within the same class, there is no problem with having one web method call another.
Suppose however that I want to separate out the web methods so that they can be exposed as two separate WSDL's. I was thinking I could set up another web service project and have the new web service call the web methods of the other web service, but I'm worried about the performance implications.
In this case, the server would be communicating on the localhost using SOAP messages, and I worry that the additional overhead might cause performance problems. I'm only worried about the performance if it would be a major bottleneck, a small loss of performance is acceptable.
Anyone have any input on this matter? Or perhaps another solution that I haven't thought of?
Thanks.
I've developed a web service in C# with VS.NET, and am planning on setting up some additional web methods that make calls to other web methods. Obviously, if I declare these web methods within the same class, there is no problem with having one web method call another.
Suppose however that I want to separate out the web methods so that they can be exposed as two separate WSDL's. I was thinking I could set up another web service project and have the new web service call the web methods of the other web service, but I'm worried about the performance implications.
In this case, the server would be communicating on the localhost using SOAP messages, and I worry that the additional overhead might cause performance problems. I'm only worried about the performance if it would be a major bottleneck, a small loss of performance is acceptable.
Anyone have any input on this matter? Or perhaps another solution that I haven't thought of?
Thanks.