Browser-based user interface and control architecture with priority attributes
First Claim
1. A computer-enabled method of processing event registrations in a browser-based user interface and control architecture of a browser-enabled device, the browser-based user interface and control architecture having a browser core, a browser framework, and a user interface, the user interface being written using a markup language, the method comprising:
- receiving an event registration, by one or more processors, the received event registration having a response unique resource identifier (URI) content and a priority field, the event registration being received by the browser framework;
examining, by the one or more processors, the priority field of the received event registration to determine priority of the received event registration;
if the browser core is loading the response URI content of a prior event registration, then determining if the priority of the received event registration is higher than the priority of the prior event registration; and
if the priority of the received event registration is higher than the priority of the prior event registration, then;
halting the loading of the response URI content of the prior event registration and starting to load the response URI content of the received event registration, andafter starting to load the response URI content of the received event registration, returning to loading the response URI content of the prior event registration,wherein the response URI content of the received event registration includes at least a portion of the user interface.
3 Assignments
0 Petitions
Accused Products
Abstract
A browser-enabled device includes a browser-based user interface and control architecture, which has a browser core, a browser framework, and a user interface. The user interface is written using a markup language. In processing event registrations, the browser framework receives an event registration. The received event registration having a response unique resource identifier (URI) content and a priority field. The priority field of the received event registration is examined to determine priority of the received event registration. If the browser core is loading the response URI content of a prior event registration and if the priority of the received event registration is higher than the priority of the prior event registration, then the loading of the response URI content of the prior event registration is halted, and loading of the response URI content of the received event registration is begun.
-
Citations
26 Claims
-
1. A computer-enabled method of processing event registrations in a browser-based user interface and control architecture of a browser-enabled device, the browser-based user interface and control architecture having a browser core, a browser framework, and a user interface, the user interface being written using a markup language, the method comprising:
-
receiving an event registration, by one or more processors, the received event registration having a response unique resource identifier (URI) content and a priority field, the event registration being received by the browser framework; examining, by the one or more processors, the priority field of the received event registration to determine priority of the received event registration; if the browser core is loading the response URI content of a prior event registration, then determining if the priority of the received event registration is higher than the priority of the prior event registration; and if the priority of the received event registration is higher than the priority of the prior event registration, then; halting the loading of the response URI content of the prior event registration and starting to load the response URI content of the received event registration, and after starting to load the response URI content of the received event registration, returning to loading the response URI content of the prior event registration, wherein the response URI content of the received event registration includes at least a portion of the user interface. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12)
-
-
13. A non-transitory computer-readable storage medium having computer-executable instructions for processing event registrations in a browser-based user interface and control architecture of a browser-enabled device, the browser-based user interface and control architecture having a browser core, a browser framework, and a user interface, the user interface being written using a markup language, comprising instructions for:
-
receiving an event registration, the received event registration having a response unique resource identifier (URI) content and a priority field, the event registration being received by the browser framework; examining the priority field of the received event registration to determine priority of the received event registration; if the browser core is loading the response URI content of a prior event registration, then determining if the priority of the received event registration is higher than the priority of the prior event registration; and if the priority of the received event registration is higher than the priority of the prior event registration, then; halting the loading of the response URI content of the prior event registration and starting to load the response URI content of the received event registration, and after starting to load the response URI content of the received event registration, returning to loading the response URI content of the prior event registration, wherein the response URI content of the received event registration includes at least a portion of the user interface. - View Dependent Claims (14, 15, 16, 17, 18)
-
-
19. A browser-enabled device, comprising:
-
a processor; memory; and a browser-based user interface and control architecture comprising; an operating system kernel; a browser core; a user interface written using the markup language; and a browser framework, the browser framework having an application programming interface (API) configured to; receive an event registration, the event registration having a response unique resource identifier (URI) content and a priority field; examine the priority field of the event registration to determine priority of the received event registration; if the browser core is loading the response URI content of a prior event registration, then determine if the priority of the received event registration is higher than the priority of the prior event registration; and if the priority of the received event registration is higher than the priority of the prior event registration, then; halt loading of the response URI content of the prior event registration and start loading the response URI content of the received event registration, and after starting to load the response URI content of the received event registration, return to loading the response URI content of the prior event registration, wherein the response URI content of the received event registration includes at least a portion of the user interface. - View Dependent Claims (20, 21, 22, 23, 24, 25, 26)
-
Specification