Flexible hierarchical settings registry for operating systems

• US 8,667,512 B2
• Filed: 08/31/2009
• Issued: 03/04/2014
• Est. Priority Date: 10/29/2008
• Status: Expired due to Fees

• Current Assignee: Qualcomm, Inc.
• Original Assignee: Qualcomm, Inc.
• Inventors: Mager, Michael
• Primary Examiner(s): Puente, Emerson
• Assistant Examiner(s): PATEL, HIREN P
• Application Number:
  US12/551,498
• Publication Number:
  US 20100138844A1
• Time in Patent Office: 1,646 Days
• Field of Search: None
• US Class Current: 719/328
• CPC Class Codes: G06F 21/6218 to a system of files or objects, e.g. local or distributed file system or database
• CPC Class Codes: G06F 9/44505 Configuring for program initiating, e.g. using registry, configuration files

Abstract

Various embodiments include methods and systems provide a distributed settings registry with access protection definable by application developers. Distributed settings registry may be implemented across different technologies with customizable privileges and the dynamic ability to plug different nodes into the registry tree. The settings registry may exist under a registry interface so the applications invoking the registry need not be concerned with where or how the settings data is stored. Each node in the tree of the registry may define its own privilege requirements and storage technology. Nodes may be “native” (i.e., fully supported within the setting registry system software) or “non-native” (i.e., defined by developers for specific applications).

Claims

1. A method for storing and accessing software settings within a registry, comprising:

creating a native node of a native data store by generating a native settings object containing a settings value;

storing the native settings object in memory with a key using a first file type, wherein the native data store is associated with the first file type, and wherein the first file type is supported by the registry;

registering the native node with the registry;

receiving a non-native node of a non-native data store, wherein the non-native data store is associated with a second file type that is not supported by the registry;

registering the non-native node with the registry using a class identifier for a custom registry class;

receiving a request for settings data from an application in the form of an application programming interface (API) call;

determining whether the requested settings data is in the native node or the non-native node; and

implementing a singleton service associated with the registry to obtain the settings value in response to determining that the requested settings data is in the native node, wherein;

the singleton service obtains the requested settings data from the native settings object within the singleton service;

the singleton service returns the obtained settings data to the API; and

the obtained settings data is returned to the application from the API.

2. The method of claim 1, wherein the singleton service controls all accesses to native settings objects.

3. The method of claim 1, further comprising:

implementing a non-native process for obtaining the requested settings data in response to determining that that the requested settings data is in the non-native node.

4. The method of claim 1, further comprising:

determining whether the application satisfies a privilege specified in the native settings object in response to determining that the requested settings data is in the native node; and

denying access to the settings data in response to determining that the application does not satisfy the privilege specified in the native settings object.

5. The method of claim 4, further comprising defining the privilege when the native settings object is generated.

6. A mobile device, comprising:

a processor;

a memory coupled to the processor;

wherein the processor is configured with processor-executable instructions to perform steps comprising;

creating a native node for a native data store by generating a native settings object containing a settings value;

storing the native settings object in memory with a key using a first file type, wherein the native data store is associated with the first file type, and wherein the first file type is supported by the registry;

registering the native node with the registry;

receiving a non-native node of a non-native data store, wherein the non-native data store is associated with a second file type that is not supported by the registry;

registering the non-native node with the registry using a class identifier for a custom registry class;

receiving a request for settings data from an application in the form of an application programming interface (API) call;

determining whether the requested settings data is in the native node or in the non-native node; and

implementing a singleton service associated with the registry to obtain the settings value in response to determining that the requested settings data is in the native node, wherein;

the singleton service obtains the settings data from the native settings object within the singleton service;

the singleton service returns the obtained settings data to the API; and

the obtained settings data is returned to the application from the API.

7. The mobile device of claim 6, wherein the processor is further configured with processor-executable instructions such that the singleton service controls all accesses to native settings objects.

8. The mobile device of claim 6, wherein the processor is further configured with processor-executable instructions to perform steps further comprising:

implementing a non-native process for obtaining the requested settings data in response to determining that that the requested settings data is in non-native node.

9. The mobile device of claim 6, wherein the processor is further configured with processor-executable instructions to perform steps further comprising:

determining whether the application satisfies a privilege specified in the native settings object in response to determining that the requested settings data is in the native node; and

denying access to the settings data in response to determining that the application does not satisfy the privilege specified in the native settings object.

10. The mobile device of claim 9, wherein the processor is configured with processor-executable instructions to perform steps further comprising defining the privilege when the native settings object is generated.

11. A non-transitory computer-readable storage medium having stored thereon processor-executable instructions configured to cause a processor of a computing device to perform steps comprising:

creating a native node in a native data store by generating a native settings object containing a settings value;

storing the native settings object in memory with a key using a first file type, wherein the native data store is associated with the first file type, and wherein the first file type is supported by the registry;

registering the native node with the registry;

receiving a non-native node of a non-native data store, wherein the non-native data store is associated with a second file type that is not supported by the registry;

registering the non-native node with the registry using a class identifier for a custom registry class;

receiving a request for settings data from an application in the form of an application programming interface (API) call;

determining whether the requested settings data is in a native node or in a non-native node; and

implementing a singleton service associated with the registry to obtain the settings value in response to determining that the requested settings data is in the native node, wherein;

the singleton service obtains the settings data from the native settings object within the singleton service;

the singleton service returns the obtained settings data to the API; and

the obtained settings data is returned to the application from the API.

12. The non-transitory computer-readable storage medium of claim 11, wherein the stored processor-executable instructions are configured to cause the processor to perform steps such that the singleton service controls all accesses to native settings objects.

13. The non-transitory computer-readable storage medium of claim 11, wherein the stored processor-executable instructions are configured to cause the processor to perform steps further comprising:

implementing a non-native process for obtaining the requested settings data in response to determining that the requested settings data is in a non-native node.

14. The non-transitory computer-readable storage medium of claim 11, wherein the stored processor-executable instructions are configured to cause the processor to perform steps further comprising:

determining whether the application satisfies a privilege specified in the native settings object in response to determining that the requested settings data is in the native node; and

denying access to the settings data in response to determining that the application does not satisfy the privilege specified in the native settings object.

15. The non-transitory computer-readable storage medium of claim 14, wherein the stored processor-executable instructions are configured to cause the processor to perform steps further comprising defining the privilege when the native settings object is generated.

16. A mobile device, comprising:

means for creating a native node in a native data store by generating a native settings object containing a settings value;

means for storing the native settings object in memory with a key using a first file type, wherein the native data store is associated with the first file type, and wherein the first file type is supported by the registry;

registering the native node with the registry;

means for receiving a non-native node of a non-native data store, wherein the non-native data store is associated with a second file type that is not supported by the registry;

means for registering the non-native node with the registry using a class identifier for a custom registry class;

means for receiving a request for settings data from an application in the form of an application programming interface (API) call;

means for determining whether the requested settings data is in the native node or in a non-native node; and

means for implementing a singleton service associated with the registry to obtain the settings value in response to determining that the requested settings data is in the native node, wherein;

the singleton service obtains the settings data from the native settings object within the singleton service;

the singleton service returns the obtained settings data to the API; and

the obtained settings data is returned to the application from the API.

17. The mobile device of claim 16, wherein means for implementing the singleton service includes means for controlling all accesses to native settings objects.

18. The mobile device of claim 16, further comprising:

implementing a non-native process for obtaining the requested settings data in response to determining that the requested settings data is in the non-native node.

19. The mobile device of claim 16, further comprising:

means for determining whether the application satisfies a privilege specified in the native settings object in response to determining that the requested settings data is in the native node; and

means for denying access to the settings data in response to determining that the application does not satisfy the privilege specified in the native settings object.

20. The mobile device of claim 19, further comprising means for defining the privilege when the native settings object is generated.