Exposing functionality over ASP.NET WebServices using best practices

Posted by Erup on Stack Overflow See other posts from Stack Overflow or by Erup
Published on 2010-05-02T17:21:04Z Indexed on 2010/05/02 17:27 UTC
Read the original article Hit count: 443

Filed under:
|
|

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

© Stack Overflow or respective owner

Related posts about .NET

Related posts about web-services