Data controls architecture

• US 7,464,386 B2
• Filed: 05/17/2004
• Issued: 12/09/2008
• Est. Priority Date: 05/17/2004
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Kothari, Nikhil, Millington, Brad, Huff, Polita, Lipton, Eilon
• Primary Examiner(s): Dam; Tuan Q.
• Assistant Examiner(s): TECKLU, ISAAC TUKU
• Application Number:
  US10/847,648
• Publication Number:
  US 20050256834A1
• Time in Patent Office: 1,667 Days
• Field of Search: 717/105, 717/106, 717/107
• US Class Current: 719/331
• CPC Class Codes: G06F 16/81 Indexing, e.g. XML tags; Data structures therefor; Storage structures
• CPC Class Codes: G06F 16/9535 Search customisation based on user profiles and personalisation
• CPC Class Codes: G06F 16/972 Access to data in other repository systems, e.g. legacy data or dynamic Web page generation

Abstract

Systems and methods for data controls architecture are described. In one aspect, a data source control exposes an interface for generic access to a data store. A data-bound control implements the interface to automatically databind to the data store at an appropriate time during runtime operations of the data-bound control.

Claims

1. A method for automatically binding data to data stores, the method comprising:

exposing, by a first data source control, a first application programming interface for generic access to a first data store having data types, wherein the first data source control represents a first data store and the capabilities of the first data store;

exposing, by a second data source control, a second application programming interface for generic access to the second data store having data types, wherein the second data source control represents a second data store and the capabilities of the second data store, and wherein the second data store is different from the first data store;

associating a first data-bound control with the first data source control, wherein the first data bound control is a visual source control whose rendering depends on the first data source control;

implementing the first application programming interface, by the first data-bound control, to automatically databind to the first data store at an appropriate time during runtime operations of the fu data-bound control, wherein the first data source control allows the manipulation of underlying data without requiring a unique application programming interface for each data type being utilized;

associating a second data-bound control with the second data source control, wherein the second data bound control is a visual source control whose rendering depends on the second data source control;

implementing the second application programming interface, by the second data-bound control to automatically databind to the second data store at an appropriate time during runtime operations of the second data-bound control, wherein the second data

source control allows the manipulation of underlying data without requiring a unique application programming interface for each data type being utilized;

determining that a value associated with, a declarative parameter maintained by the first data source control has changed; and

responsive to the determining, raising by the first data source control, a parameter changed event causing the first data-bound control to re-bind to the first data store.

2. A method as recited in claim 1, wherein the first data source control is a reusable component.

3. A method as recited in claim 1, wherein the generic access is independent of any specific data store or data type.

4. A method as recited in claim 1, wherein the generic access comprises access to data and/or operations associated with a particular data store, the data being tabular or hierarchical data.

5. A method as recited in claim 1, wherein the first data store is associated with database data, markup, file system data, a Universal Resource Identifier, or business data.

6. A method as recited in claim 1, wherein the first data store is a data object, an SQL data source, or a markup data source.

7. A method as recited in claim 1, wherein the method further comprises automatically paging, by the first data-bound control, over data associated with the first data store via the first application programming interface.

8. A method as recited in claim 1, wherein the method further comprises automatically caching, by the first data source control, of first data store data.

9. A method as recited in claim 1, wherein the method further comprises:

automatically caching, by the first data source control, of first data store data; and

automatic invalidation and purging of cached data when data of the first data store changes.

10. A method as recited in claim 1, and further comprising dynamically discovering, by the first data-bound control, operations promoted by a data source view exposed by the first application programming interface, the operations being associated with the first data store.

11. A method as recited in claim 1, and further comprising:

dynamically discovering, by the first data-bound control, operations promoted by a data source view exposed by the first application programming interface, the operations being associated with the first data store; and

presenting or disabling, by the first data-bound control, a user interface element to reflect supported or non-supported operations of the operations.

12. A method as recited in claim 1, and further comprising:

receiving a request from the first data-bound control to implement a dynamically discovered operation promoted to the first data-bound control by a respective portion of the first application programming interface;

implementing the dynamically discovered operation, by the first data source control;

responsive to implementing, receiving data from the first data store; and

communicating, by the first data source control, the data to a callback of the data-bound control.

13. A method as recited in claim 1, and further comprising navigating, by the first data-bound control, parent-child relationships in hierarchical data associated with the first data store, the navigating being based on a data source view provided by the first application programming interface.

14. A method as recited in claim 1, and further comprising rendering, by the first data-bound control, information associated with the first data store as a function of a data source view provided by the first application programming interface.

15. A method as recited in claim 14, wherein the rendering is an expanded tree view or menu.

16. A method as recited in claim 1, wherein the method further comprises:

automatically implementing, by the first data-bound control, parameterized runtime operations with respect to the first data store via the first application programming interface, the automatic implementing being independent of any page developer code to handle any parameter; and

identifying with declarative parameters underlying the first application programming interface, how parameter values associated with respective ones of the runtime operations are to be evaluated at runtime.

17. A method as recited in claim 16, the parameterized operations include select, insert, update, or delete data operations.

18. A method as recited in claim 16, wherein the declarative parameters are specified in a tag-based data format.

38. A method as recited in claim 1, wherein the first data-bound control and the second data-bound control provide different functionality.

39. A method as recited in claim 1, wherein the first application programming interface and the second application programming interface provide different functionality.

19. A computer-storage medium comprising computer-executable instructions for a data controls architecture, the computer-executable instructions comprising instructions for:

exposing, by a first data source control, a first application programming interface for generic access to a first data store having data types, wherein the first data source control represents the first data store and the capabilities of the first data store;

exposing, by a second data source control, a second application programming interface for generic access to the second data store having data types, wherein the second data source control represents a second data store and the capabilities of the second data store, and wherein the second data store is different from the first data store;

associating a first data-bound control with the first data source control, wherein the first data bound control is a visual source control whose rendering depends on the data source control;

implementing the first application programming interface, by the first data-bound control, to automatically databind to the first data store at an appropriate time during runtime operations of the first data-bound control, wherein the first data source control allows the manipulation of underlying data without requiring a unique application programming interface for each data type being utilized, wherein the first data source control allows the manipulation of underlying data without requiring a unique application programming interface for each data type being utilized;

associating a se and data-bound control with the second data source control, wherein the second data bound control is a visual source control whose rendering depends on the second data source control; and

implementing the second application programming interface, by the second data-bound control to automatically databind to the second data store at an appropriate time during runtime operations of the second data-bound control, wherein the second data source control allows the manipulation of underlying data without requiring a unique application programming interface for each data type being utilized;

determining that a value associated with a declarative parameter maintained the first data source control has changed;

responsive to the determining, raising by the first data source control, a parameter changed event causing the fist data-bound control to re-bind to the first data store;

providing a user interface element to support generic access to the first and second data stores;

dynamically discovering, by the first data-bound control, operations supported by the first data store;

disabling, by the first data-bound control, the user interface element to the extent the user interface element reflects operations not supported by the first data store; and

presenting the user interface element to reflect operations supported by the first data store.

20. A computer-storage medium as recited in claim 19 wherein the generic access is independent of any specific data store or data type.

21. A computer-storage medium as recited in claim 19, wherein the first data store is associated with database data, markup, file system data, a Universal Resource Identifier, or business data.

22. A computer-storage medium as recited in claim 19, and further comprising computer-executable instructions for:

receiving a request from the first data-bound control to implement a dynamically discovered operation promoted to the first data-bound control by a respective portion of the first application programming interface;

implementing the dynamically discovered operation, by the first data source control;

responsive to implementing, receiving data from the first data store; and

communicating, by the first data source control, the data to a callback of the data-bound control.

23. A computer-storage medium as recited in claim 19, and further comprising computer-executable instructions for navigating, by the first data-bound control, parent-child relationships in hierarchical data associated with the first data store, the navigating being based on a data source view provided by the first application programming interface.

24. A computer-storage medium as recited in claim 19, and further comprising computer-executable instructions for:

automatically implementing, by the first data-bound control, parameterized runtime operations with respect to the first data store via the first application programming interface, the automatic implementing being independent of any page developer code to handle any parameter, and

identifying with declarative parameters underlying the first application

programming interface, how parameter values associated with respective ones of the runtime operations are to be evaluated at runtime.

25. A computer-storage medium as recited in claim 24, wherein the parameterized operations include select, insert, update, or delete data operations.

26. A computer-storage medium as recited in claim 24, wherein the declarative parameters are specified in a tag-based data format.

27. A computing device comprising:

a processor; and

a memory coupled to the processor, the memory comprising computer-program instructions executable by the processor for;

exposing, by a first data source control, a first application programming interface for generic access to a first data store, wherein the first data source control represents the first data store and the capabilities of the first data store;

exposing, by a second data source control, a second application programming interface for generic access to the second data store, wherein the second data source control represents a second data store and the capabilities of the second data store, and wherein the second data store is different from the first data store;

associating a first data-bound control with the first data source control, wherein the first data bound control is a visual source control whose rendering depends on the first data source control;

implementing the first application programming interface, by the first data-bound control, to automatically databind to the first data store at an appropriate time during runtime operations of the data-bound control, wherein the first data source control allows the manipulation of underlying data without requiring a unique application programming interface for each data type being utilized;

associating a second data-bound control with the second data source control wherein the second data bound control is a visual source control whose rendering depends on the second data source control; and

implementing the second application programming interface, by the second data-bound control to automatically databind to the second data store at an appropriate time during runtime operations of the second data-bound control, wherein the second data source control allows the manipulation of underlying data without requiring a unique application programming interface for each data type being utilized;

determining, that a value associated with a declarative parameter maintained by the first data source control has changed; and

responsive to the determination, raising by the first data source control, a parameter changed event causing the data-bound control to re-bind to the first data store.

28. A computing device as recited in claim 27, wherein the generic access is independent of any specific data store or data type.

29. A computing device as recited in claim 27, wherein the first data store is associated with database data, markup, file system data, a Universal Resource Identifier, or business data.

30. A computing device as recited in claim 27, and further comprising computer-programmable instructions for dynamically discovering, by the first data-bound control, operations promoted by a data source view exposed by the first application programming interface, the operations being associated with the first data store.

31. A computing device as recited in claim 27, and further comprising computer-programmable instructions for:

dynamically discovering, by the first data-bound control, operations promoted by a data source view exposed by the first application programming interface, the operations being associated with the first data store; and

presenting or disabling, by the first data-bound control, a user interface element to reflect supported or non-supported operations of the operations.

32. A computing device as recited in claim 27, and further comprising computer-programmable instructions for:

receiving a request from the first data-bound control to implement a dynamically discovered operation promoted to the first data-bound control by a respective portion of the first application programming interface;

implementing the dynamically discovered operation, by the first data source control;

responsive to implementing, receiving data from the first data store; and

communicating, by the first data source control, the data to a callback of the data-bound control.

33. A computing device as recited in claim 27, and further comprising computer-programmable instructions for navigating, by the first data-bound control, parent-child relationships in hierarchical data associated with the first data store, the navigating being based on a data source view provided by the first application programming interface.

34. A computing device as recited in claim 27, and further comprising computer-programmable instructions for:

automatically implementing, by the first data-bound control, parameterized runtime operations with respect to the first data store via the first application programming interface, the automatic implementing being independent of any page developer code to handle any parameter; and

identifying with declarative parameters underlying the first application programming interface, how parameter values associated with respective ones of the runtime operations are to be evaluated at runtime.

35. A computer-storage medium comprising computer-executable instructions for a data controls architecture, the computer-executable instructions comprising instructions for:

exposing, by a first data source control, a first application programming interface for generic access to a first data store having data types, wherein the first data source control represents the first data store and the capabilities of the first data store;

exposing, by a second data source control, a second application programming interface for generic access to the second data store, wherein the second data source control represents a second data store and the capabilities of the second data store, and wherein the second data store is different from the first data store;

providing a user interface element to support generic access to the first and second data stores;

associating a first data-bound control with the first data source control;

implementing the first application programming interface, by the first data-bound control, to automatically databind to the first data store at an appropriate time during runtime operations of the first data-bound control, wherein the first data source control allows the manipulation of underlying data without requiring a unique application programming interface for each data type being utilized;

associating a second data-bound control with the second data source control wherein the second data bound control is a visual source control whose rendering depends on the second data source control; and

implementing the second application programming interface, by the second data-bound control to automatically databind to the second data store at an appropriate time during runtime operations of the second data-bound control, wherein the second data source control allows the manipulation of underlying data without requiring a unique application programming interface for each data type being utilized;

dynamically discovering, by the first data-bound control, operations supported by the first data store;

disabling, by the first data-bound control, the user interface element to the extent the user interface element reflects operations not supported by the first data store;

presenting the user interface element to reflect operations supported by the first data store;

automatically implementing, by the first data-bound control, parameterized runtime operations with respect to the first data store via the first application programming interface, the automatic implementing being independent of any page developer code to handle any parameter; and

identifying with declarative parameters underlying the first application programming interface, how parameter values associated with respective ones of the runtime operations are to be evaluated at runtime.

36. A method as recited in claim 35, wherein the first data-bound control and the second data-bound control provide different functionality.

37. A method as recited in claim 35, wherein the first application programming interface and the second application programming interface provide different functionality.