Exposing functionality over ASP.NET WebServices using best practices
- by Erup
In terms of performance, IIS process management and reliability, is there a best practice in how to expose functionality over ASP.NET webservices?
Like:
Each consulting service in a specific asmx (like consultA.asmx)
All consulting services in one asmx (like consults.asmx)
NOTE: In this case, I cannot use WCF