Registry for app features referenced pointers and pointer definitions

• US 10,318,360 B2
• Filed: 10/31/2017
• Issued: 06/11/2019
• Est. Priority Date: 06/05/2013
• Status: Active Grant

• Current Assignee: Splunk Inc. (Cisco Systems, Inc.)
• Original Assignee: Splunk Inc. (Cisco Systems, Inc.)
• Inventors: Neeman, Itay A.
• Primary Examiner(s): Bragdon, Reginald G
• Assistant Examiner(s): Verdi, Kimbleann C
• Application Number:
  US15/799,618
• Publication Number:
  US 20180052721A1
• Time in Patent Office: 588 Days
• Field of Search: None
• CPC Class Codes: G06F 16/2455 Query execution
• CPC Class Codes: G06F 2209/545 Gui
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management
• CPC Class Codes: G06F 9/44521 Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
• CPC Class Codes: G06F 9/54 Interprogram communication
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications

Abstract

A first feature (e.g., chart or table) includes a reference to a dynamic pointer. Independently, the pointer is defined to point to a second feature (e.g., a query). The first feature is automatically updated to reflect a current value of the second feature. The reference to the pointer and pointer definition are recorded in a central registry, and changes to the pointer or second feature automatically cause the first feature to be updated to reflect the change. A mapping between features can be generated using the registry and can identify interrelationships to a developer. Further, changes in the registry can be tracked, such that a developer can view changes pertaining to a particular time period and/or feature of interest (e.g., corresponding to an operation problem).

Claims

1. A method for using a registry to facilitate app development, comprising sending one or more libraries of code to a client device, wherein the one or more libraries cause the client device to perform, during execution of application code that references the one or more libraries of code, operations comprising:

automatically registering a detected first app feature, a detected pointer and a detected pointer definition for the pointer in a registry, wherein the pointer definition associates the pointer with a second app feature;

responsive to detecting that the first app feature references the pointer and responsive to detecting the pointer definition, automatically registering the first app feature in the registry to receive notifications about events pertaining to the second app feature; and

responsive to detecting a change associated with the second app feature, notifying the first app feature about the change associated with the second app feature.

2. The method of claim 1,

wherein the automatically registering the detected first app feature in the registry includes an indication that the first app feature is empty, and

responsive to subsequently detecting a feature definition for the first app feature, automatically registering the feature definition in the registry in association with the first app feature.

3. The method of claim 1, wherein the operations additionally comprise, responsive to detecting that the first app feature references the pointer, automatically registering the first app feature in the registry to receive notifications about events pertaining to the pointer.

4. The method of claim 3,

wherein the automatically registering the detected pointer in the registry includes an indication that the pointer is empty;

and

wherein the automatically registering the first app feature in the registry to receive notifications about events pertaining to the pointer occurs before detecting the detected pointer definition for the pointer.

5. The method of claim 1, wherein the operations additionally comprise, responsive to detecting the change associated with the second app feature, identifying relevant app features that are registered in the registry to receive notifications about events pertaining to the second app feature, wherein the relevant app features include the first app feature.

6. The method of claim 1, wherein the change associated with the second app feature includes at least one of:

a new registration of the second app feature;

a change to the second app feature'"'"'s definition;

a change to the second app feature;

or

a removal of the second app feature.

7. The method of claim 1, wherein the first app feature responds to the notifying the first app feature by updating data presented by the first app feature to reflect data in the second app feature.

8. The method of claim 1, wherein the one or more libraries of code further cause the client device to track a history of modifications to the registry.

9. The method of claim 1, wherein the one or more libraries of code further cause the client device to:

track a history of events that modify the registry; and

present a visual timeline of the events in the history.

10. The method of claim 1, wherein the one or more libraries of code further cause the client device to generate, based on the registry, a map of interrelationships between at least some app features.

11. One or more non-transitory computer storage media storing computer-useable instructions that, when used by one or more computing devices, cause the one or more computing devices to perform operations comprising:

automatically registering a detected first app feature, a detected pointer and a detected pointer definition for the pointer in a registry, wherein the pointer definition associates the pointer with a second app feature;

responsive to detecting that the first app feature references the pointer and responsive to detecting the pointer definition, automatically registering the first app feature in the registry to receive notifications about events pertaining to the second app feature; and

responsive to detecting a change associated with the second app feature, notifying the first app feature about the change associated with the second app feature.

12. The non-transitory media of claim 11,

wherein the automatically registering the detected first app feature in the registry includes an indication that the first app feature is empty, and

responsive to subsequently detecting a feature definition for the first app feature, automatically registering the feature definition in the registry in association with the first app feature.

13. The non-transitory media of claim 11, wherein the operations additionally comprise, responsive to detecting that the first app feature references the pointer, automatically registering the first app feature in the registry to receive notifications about events pertaining to the pointer.

14. The non-transitory media of claim 13,

wherein the automatically registering the pointer in the registry includes an indication that the pointer is empty;

and

wherein the automatically registering the first app feature in the registry to receive notifications about events pertaining to the pointer occurs before the detecting of the pointer definition for the pointer.

15. The non-transitory media of claim 11, wherein the operations additionally comprise, responsive to detecting the change associated with the second app feature, identifying relevant app features that are registered in the registry to receive notifications about events pertaining to the second app feature, wherein the relevant app features include the first app feature.

16. The non-transitory media of claim 11, wherein the change associated with the second app feature includes at least one of:

a new registration of the second app feature;

a change to the second app feature'"'"'s definition;

a change to the second app feature;

or

a removal of the second app feature.

17. The non-transitory media of claim 11, wherein the first app feature responds to the notifying the first app feature by updating data presented by the first app feature to reflect data in the second app feature.

18. The non-transitory media of claim 11, wherein the operations additionally comprise tracking a history of modifications to the registry.

19. The non-transitory media of claim 11, wherein the operations additionally comprise:

tracking a history of events that modify the registry; and

presenting a visual timeline of the events in the history.

20. The non-transitory media of claim 11, wherein the operations additionally comprise generating, based on the registry, a map of interrelationships between at least some app features.

21. A computer system comprising:

a server comprising one or more hardware processors and memory configured to provide computer program instructions to the one or more hardware processors, wherein the server is configured to utilize the one or more hardware processors to send one or more libraries of code to a client device, wherein the one or more libraries cause the client device to perform, during execution of application code that references the one or more libraries of code, operations comprising;

automatically registering a detected first app feature, a detected pointer and a detected pointer definition for the pointer in a registry, wherein the pointer definition associates the pointer with a second app feature;

responsive to detecting that the first app feature references the pointer and responsive to detecting the pointer definition, automatically registering the first app feature in the registry to receive notifications about events pertaining to the second app feature; and

responsive to detecting a change associated with the second app feature, notifying the first app feature about the change associated with the second app feature.

22. The computer system of claim 21,

wherein the automatically registering the detected first app feature in the registry includes an indication that the first app feature is empty, and

wherein the operations additionally comprise, responsive to subsequently detecting a feature definition for the first app feature, automatically registering the feature definition in the registry in association with the first app feature.

23. The computer system of claim 21, wherein the operations additionally comprise, responsive to detecting that the first app feature references the pointer, automatically registering the first app feature in the registry to receive notifications about events pertaining to the pointer.

24. The computer system of claim 23,

wherein the automatically registering the pointer in the registry includes an indication that the pointer is empty;

and

wherein the automatically registering the first app feature in the registry to receive notifications about events pertaining to the pointer occurs before the detecting of the pointer definition for the pointer.

25. The computer system of claim 21, wherein the operations additionally comprise, responsive to detecting the change associated with the second app feature, identifying relevant app features that are registered in the registry to receive notifications about events pertaining to the second app feature, wherein the relevant app features include the first app feature.

26. The computer system of claim 21, wherein the change associated with the second app feature includes at least one of:

a new registration of the second app feature;

a change to the second app feature'"'"'s definition;

a change to the second app feature;

or

a removal of the second app feature.

27. The computer system of claim 21, wherein the first app feature responds to the notifying the first app feature by updating data presented by the first app feature to reflect data in the second app feature.

28. The computer system of claim 21, wherein the one or more libraries of code further cause the client device to track a history of modifications to the registry.

29. The computer system of claim 21, wherein the one or more libraries of code further cause the client device to:

track a history of events that modify the registry; and

present a visual timeline of the events in the history.

30. The computer system of claim 21, wherein the one or more libraries of code further cause the client device to generate, based on the registry, a map of interrelationships between at least some app features.