Designing Web services for AJAX Consumption -


We're in the process of designing / creating web services that are comfortable using XHR calls from different web pages. Customer side will be consumed. These web pages will include those components that will come from data collected from web services.

My question is, why would specifically customer-side components be needed for each page? Therefore, only one XHR call will be required to populate a specific AJAX component or to retrieve all the data needed to update a specific page. Or more advice is given to develop generic web services, for example, match a database schema, and many XHR call clients are needed so that all data can be retrieved to populate the AJAX component Could it? There is some messy coding to call the series from the second point of view, so that all the data needed before updating an AJAX component can be obtained.

Hope this makes sense

You always depend on those services Should design on what they have to provide. Unless you need any service that receives rows from the database, do not create one. You may find that you need a service that returns to full business entities - they can be in multiple tables.

Or, you may need just one service to provide data for UI controls. In that case, you should do this later you can find out that two operations return almost the same data , So that you can perform two operations, which gives data for both.


Comments

Popular posts from this blog

c# - ListView onScroll event -

PHP - get image from byte array -

Linux Terminal Problem with Non-Canonical Terminal I/O app -