Depending on the type of jQuery app you're building, WCF provides an easy way to build a service to supply data to it. Suppose your application is a forms-over-data app or any other collection-based app
. In this case you have some data in a database on the server and your app aims to expose that data in a grid or some other control. WCF DomainService
is perfect here with its support for client or server-side querying, client-side data change events and change tracking through the $.dataSource plugin, client and server-side validation, as well as server-side support for Entity Data Model.
If your app does not fit into that shape (in other words you are building a more general-purpose app
), you can drop down and take control of your $.ajax requests. In this case you would use a regular WCF Service
, which gives you fine-grained control over data formats, the URI structure, exact service operations, and so on.
Next to each scenario, you will find our assessment of how feature complete is the scenario implementation.1. Data-driven application working with a collection of entities (RIA/JS) In Progress
Another very common scenario is managing a collection of objects, in a pattern many call forms over data. The user can perform CRUD operations on the entities in the collection using a list or grid view combined with a form on the client side. Changes are aggregated and validated before they are submitted back to the service This pattern lends itself very well to applications such as an expense report tracker or a contact manager.2. Submitting HTML form data to a service In Progress
Jeff HandleyTomasz JanczukYavor GeorgievCarlos Figueira
To file a bug against features from this project, please use the Issue Tracker tab. Be sure to select "jQuery" as the component when filing a bug.