Assume that I have an asp.net page that will go to the server after the client side event and "some things" and UI show a return value of this process on subsequent programs.
My question is, if I am working in the same domain, then how should I make a web service and decide about that call, just to increase a post-back up and only on the ASPX page " Some stuff "to handle?
When working in the same domain to overcome some processes, what does the position of creating web-service become meaningful?
There are no hard and fast rules, however, I can offer some high-level directions:
- As a result, a significant markup (HTML, JS, etc.) is included or simplified by generating results to gain access to the situation from the original page. Keep in mind that the page object takes an important overhead over it.
- Give priority to a web service for those queries that can be parametatized and return structured data back
- Prefer a HTTPHandler for the query with simple parameters that are simple, Return full-custom text or binary (such as an image)
No comments:
Post a Comment