Simple task like make AJAX request , pass one parameter and return result, can be done with Web Service and IHttpHandler, so where is the difference ?
相关问题
- How to upgrade/install Upstart deamon version 1.5
- There Was No Endpoint Listening at http // That Co
- Starting an Application from Windows Service
- Symfony Basic Translation Example
- Intershop 7.10. - fetching payment configuration
相关文章
- Service层和Dao层一定要对应吗?
- k8s 访问Pod 时好时坏
- Async task does not work properly (doInBackground
- Keeping alive Intent Service after application is
- A proper way to Debug a Service in Android Studio?
- Simple service in Swift, persists, foreground only
- Running msiexec from a service (Local System accou
- Symfony 3 - Define form as a service
ASP.NET web services are in fact a type of HttpHandler that provide an XML based communication infrastructure based on W3C standards (SOAP/WSDL). This means that non .NET clients can interoperate with ASP.NET web services. In your case where you're making a very simple single ajax request to return a simple result, ASP.NET/XML web services may be overkill.
It may be more beneficial/efficient to implement a simple custom HttpHandler rather than invoking all of the plumbing and overhead associated with ASP.NET web services. With a custom HttpHandler you can just send the parameter you need and return exactly the result you want to see without any of the supporting SOAP xml that would be created when using XML web services.