Back to results
US 10,769,234 B2Granted
Document object model transaction crawler
AssigneeMicro Focus LLC
InventorsThomas Christopher Swedlund, Kevin Allen Williams, Brian Charles King
Life of this patent
Estimating the term…
Abstract
Examples herein involve a document object model (DOM) transaction crawler. Examples herein involve identifying an event in a first state of a document object model. The event is executed to cause a state change from the first state of the document object model to a second state of the document object model. Furthermore, the state change is stored in a transaction log to store the difference between the first state of the document object model and the second state of the document object model.
Claims20
A method performed by a system comprising a hardware processor, comprising:
- identifying a first event in a first state of a document object model (DOM) of an application;
- executing the first event to cause a first state change from the first state of the DOM to a second state of the DOM;
- recording the first state change in a transaction log, the first state change comprising a difference between the first state of the DOM and the second state of the DOM, wherein the transaction log further contains a plurality of state changes of the DOM, the plurality of state changes comprising a second state change recorded in the transaction log responsive to a second event that caused the second state change of the DOM;
- and
- reverting the DOM from the second state of the DOM to the first state of the DOM;
- and
- after reverting the DOM from the second state to the first state,
- retrieving the plurality of state changes from the transaction log,
- implementing the plurality of state changes retrieved from the transaction log to traverse the DOM from the first state to a third state of the DOM without re-executing the first event and the second event, and
- execute a third event to cause a further state change of the DOM from the third state to another state of the DOM.
7 more elements
A non-transitory machine readable medium comprising instructions that, when executed, cause a machine to:
- identify a first state change in a document object model (DOM) of an application in response to executing a first event of a first state of the DOM, the first state change comprising a difference between the first state of the DOM and a second state of the DOM;
- store the first state change in a transaction log, wherein the transaction log further contains a plurality of state changes of the DOM, the plurality of state changes comprising a second state change recorded in the transaction log responsive to a second event that caused the second state change of the DOM;
- after the first state change from the first state of the DOM to the second state of the DOM, revert the DOM from the second state of the DOM to the first state of the DOM;
- and
- after reverting the DOM from the second state to the first state,
- retrieve the plurality of state changes from the transaction log,
- implement the plurality of state changes retrieved from the transaction log to traverse the DOM from the first state to a third state of the DOM without re-executing the first event and the second event, and
- execute a third event to cause a further state change of the DOM from the third state to another state of the DOM.
5 more elements
An apparatus comprising:
- a processor;
- and
- a non-transitory storage medium storing instructions executable on the processor to:
- identify a first event in a first state of a document object model (DOM) of an application;
- execute the first event to cause a first state change from the first state of the DOM to a second state of the DOM;
- record the first state change in a transaction log, wherein the transaction log further contains a plurality of state changes of the DOM, the plurality of state changes comprising a second state change recorded in the transaction log responsive to a second event that caused the second state change of the DOM:
- revert the DOM from the second state of the DOM to the first state of the DOM;
- and
- after reverting the DOM from the second state to the first state,
- retrieve the plurality of state changes from the transaction log,
- implement the plurality of state changes retrieved from the transaction log to traverse the DOM from the first state to a third state of the DOM without re-executing the first event and the second event, and
- execute a third event to cause a further state change of the DOM from the third state to another state of the DOM.
9 more elements
Dependencies are inferred from the claim text.