Journalling non-navigation activity in a navigation-based application

• US 7,246,130 B2
• Filed: 02/19/2004
• Issued: 07/17/2007
• Est. Priority Date: 02/19/2004
• Status: Expired due to Fees

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Alcazar, Mark A., Goodwin, Margaret
• Primary Examiner(s): Cottingham; John
• Assistant Examiner(s): Lu; Kuen S.
• Application Number:
  US10/782,052
• Publication Number:
  US 20050187970A1
• Time in Patent Office: 1,244 Days
• Field of Search: 707/204, 707/101, 707/102, 707/10, 715/513
• US Class Current: 1/1
• CPC Class Codes: G06F 16/955 using information identifiers, e.g. uniform resource locators [URL]
• CPC Class Codes: Y10S 707/99942 Manipulating data structure, e.g. compression, compaction, compilation
• CPC Class Codes: Y10S 707/99943 Generating database or data structure, e.g. via user interface

Abstract

The mechanisms and techniques described in this document are directed to a journal that allows a navigation-based application to store and restore state of a resource that is programmatically altered. A resource may invoke code that creates and stores an entry in the journal. The entry includes sufficient information to restore the resource from one state to its prior state. In addition, the entry includes a mechanism for creating another entry to undo any changes made by the first entry. In this manner, the journal includes both entries that identify navigations from one resource to another, and entries may be added to undo changes to a resource to restore the resource to a prior state.

Claims

1. A system for managing changes in state of a navigation-based application, comprising:

a local computer implemented journal engine for maintaining a journal,

wherein the journal is associated with a container that navigates to and hosts a resource and the resource includes a mechanism that stores a journal entry in the journal,

wherein the journal entry includes information about a change in state of the resource and the journal entry restores the resource to the state prior to the change,

wherein the journal maintains navigation-related information about locations to which a user has navigated and provides users backward and forward access to;

(1) navigation activities in which the user has navigated backward and forward through distinct resources, and

(2) activities where a user has not conducted a physical navigation away from a resource but rather has changed a state of a resource,

wherein the backward and forward access is implemented using stack-based techniques, wherein;

individual journal entries are replayed to return a new journal entry that undoes a previously-performed action, wherein;

if the new journal entry is being replayed as a result of a backward navigation, an associated returned journal entry is placed in a forward stack, and

if the new journal entry is being replayed as a result of a forward navigation, an associated returned journal entry is placed in a back stack.

2. The system recited in claim 1, wherein the change in state of the resource is initiated by input from a user interacting with the resource.

3. The system recited in claim 1, wherein the resource is associated with a navigation-based application.

4. The system recited in claim 2, wherein the navigation-based application comprises a plurality of resources and includes a mechanism for navigating among each of the plurality of resources.

5. The system recited in claim 3, wherein the navigation-based application is browser-hosted.

6. The system recited in claim 3, wherein the navigation-based application is stand-alone.

7. The system recited in claim 1, wherein the resource further includes a mechanism for altering the state of the resource.

8. A plurality of computer executable components embodied on a computer-readable storage medium for managing changes in state of a navigation-based application, the plurality of computer-executable components comprising:

a resource including a mechanism for altering a state of the resource from a first state to a second state; and

an instance of a journal entry having a method for restoring the resource from the first state to the second state,

wherein the method further creates a journal entry to undo the restoration of the resource from the first state to the second state,

wherein the method adds to a forward stack when the method is called on a back navigation, and adds to a back stack when the method is called on a forward navigation,

wherein the journal entry comprises part of a Journal that maintains navigation-related information about locations to which a user has navigated and resources whose state has been changed by the user, and provides users backward and forward access to;

(1) navigation activities in which the user has navigated backward and forward through distinct resources, and

(2) activities where a user has not conducted a physical navigation away from a resource but rather has changed a state of a resource,

wherein the backward and forward access is implemented using stack-based navigation techniques, wherein;

individual journal entries are replayed to return a new journal entry that undoes a previously-performed action, wherein;

if the new journal entry is being replayed as a result of a backward navigation, an associated returned journal entry is placed in a forward stack, and

if the new journal entry is being replayed as a result of a forward navigation, an associated returned journal entry is placed in a back stack.

9. The computer-readable storage medium of claim 8, wherein the resource is further configured to cause the journal entry to be added to a journal that includes information about navigations among a plurality of resources.

10. The computer-readable storage medium of claim 8, wherein the resource is a component of the navigation-based application.

11. The computer-readable storage medium of claim 8, wherein the navigation-based application includes a plurality of resources that are hyperlinked together.

12. A data structure embodied on a computer-readable storage medium, the data structure comprising:

a journal entry having a Replay method, wherein the Replay method restores a resource from a first state to a second state, wherein the Replay method further creates a second journal entry to restore the resource from the second state to the first state,

wherein the journal maintains navigation-related information about locations to which a user has navigated and provides users backward and forward access to;

(1) navigation activities in which the user has navigated backward and forward through distinct resources, and

(2) activities where a user has not conducted a physical navigation away from a resource but rather has changed a state of a resource,

wherein the backward and forward access is implemented using stack-based techniques, wherein;

individual journal entries are replayed to return a new journal entry that undoes a previously-performed action, wherein;

if the new journal entry is being replayed as a result of a backward navigation, an associated returned journal entry is placed in a forward stack, and

if the new journal entry is being replayed as a result of a forward navigation, an associated returned journal entry is placed in a back stack.

13. The computer-readable storage medium of claim 12, wherein the resource comprises a component of a navigation-based application.

14. The computer-readable storage medium of claim 12, wherein the journal is associated with a window of the navigation based application.

15. The computer-readable storage medium of claim 12, wherein the journal is associated with a session.

16. The computer-readable storage medium of claim 15, wherein the session comprises a browser session.

17. The computer-readable storage medium of claim 15, wherein the session comprises a lifetime of the navigation-based application.

18. A software architecture embodied on a computer-readable storage medium for managing changes in state of a navigation-based application, the storage architecture comprising:

an internal system that supports the maintenance of entries in a journal, wherein the journal maintains state information related to navigations among resources in a navigation-based application; and

a set of interfaces that support the inclusion of entries in the journal, wherein the journal entries are related to non-navigation activity,

wherein the journal maintains navigation-related information about locations to which a user has navigated and provides users backward and forward access to;

(1) navigation activities in which the user has navigated backward and forward through distinct resources, and

(2) activities where a user has not conducted a physical navigation away from a resource but rather has changed a state of a resource,

wherein the backward and forward access is implemented using stack-based techniques, wherein;

individual journal entries are replayed to return a new journal entry that undoes a previously-performed action, wherein,

if the new journal entry is being replayed as a result of a backward navigation, an associated returned journal entry is placed in a forward stack, and

if the new journal entry is being replayed as a result of a forward navigation, an associated returned journal entry is placed in a back stack.

19. The software architecture recited in claim 18, wherein the set of interfaces includes an AddEntry method for adding a journal entry to the journal.

20. The software architecture recited in claim 18, wherein the set of interfaces includes a RemoveEntry method for removing a journal entry from the journal.

21. The software architecture recited in claim 20, wherein the RemoveEntry method is further configured to remove a journal entry from a Back stack portion of the journal.

22. The software architecture recited in claim 18, wherein the set of interfaces is provided by a base class having a Name property that identifies a name of the journal entry in the journal.

23. The software architecture recited in claim 18, wherein the set of interfaces is provided by a base class having a Replay method configured to restore a resource from a first state to a second state.

24. The software architecture recited in claim 23, wherein the Replay method is further configured to create and return a second journal entry for inclusion in the journal.

25. The software architecture recited in claim 24, wherein the second journal entry is configured to restore the resource from the second state to the first state.

26. A computer-readable storage medium encoded with instructions executing on a computer, wherein the instructions perform steps comprising:

receiving a notification to add a journal entry to a journal, wherein the journal entry is associated with a resource and the resource includes information to restore the resource from a first state to a second state, wherein

the first state is associated with a first set of characteristics of the resource and the second state is associated with a second set of characteristics of the resource; and

adding the journal entry to the journal,

wherein the journal maintains navigation-related information about locations to which a user has navigated and provides users backward and forward access to;

(1) navigation activities in which the user has navigated backward and forward through distinct resources, and

(2) activities where a user has not conducted a physical navigation away from a resource but rather has changed a state of a resource,

wherein the backward and forward access is implemented using stack-based techniques, wherein;

individual journal entries are replayed to return a new journal entry that undoes a previously-performed action, wherein;

if a the new journal entry is being replayed as a result of a backward navigation, an associated returned journal entry is placed in a forward stack, and

if the new journal entry is being replayed as a result of a forward navigation, an associated returned journal entry is placed in a back stack.

27. The computer-readable storage medium of claim 26, wherein the journal entry further comprises a mechanism for restoring the resource from the second state to the first state.

28. The computer-readable storage medium of claim 27, wherein the mechanism is configured to create a second journal entry having sufficient information to restore the resource from the second state to the first state.