1. A method of maintaining a printhead in an operable condition andor remediating a printhead to an operable condition, said method comprising the steps of:
(i) providing a maintenance roller having an elastically deformable contact surface for sealing engagement with an ink ejection face of said printhead;
(ii) moving said roller into a first position in which a clean part of said contact surface is sealingly engaged with said face, said movement being such that said contact surface progressively contacts said face during engagement;
(iii) moving said roller into a second position in which said contact surface is disengaged from said face, said movement being such that said contact surface peels away from said face during disengagement, thereby providing an inked part of said contact surface;
(iv) rotating said roller such that said inked part of said contact surface is conveyed away from said printhead and cleaned; and
(v) optionally repeating steps (ii) to (iv),
wherein said maintenance roller does not rotate when sealingly engaged with said face.
2. The method of claim 1, wherein said maintenance roller is moved substantially perpendicularly with respect to said face in steps (ii) and (iii).
3. The method of claim 1, wherein said maintenance roller is substantially coextensive with said printhead.
4. The method of claim 1, wherein said contact surface is substantially uniform.
5. The method of claim 1, wherein said maintenance roller comprises a rigid core having an elastically deformable shell, said contact surface being an outer surface of said shell.
6. The method of claim 5, wherein said shell is comprised of silicone or polyurethane.
7. The method of claim 1, wherein said maintenance roller is offset from said printhead.
8. The method of claim 1, wherein a peel zone between said contact surface and said ink ejection face advances transversely across said face during engagement in step (ii) and retreats transversely across said face during disengagement in step (iii).
9. The method of claim 1, wherein said peeling disengagement in step (iii) draws ink from said printhead onto said contact surface.
10. The method of claim 1, wherein said inked contact surface is cleaned in step (iv) by transferring said ink onto a transfer roller engaged with said maintenance roller, said transfer roller receiving ink from said maintenance roller when said maintenance roller is rotated.
11. The method of claim 10, wherein said transfer roller has a wetting surface for receiving ink from said contact surface.
12. The method of claim 11, wherein said transfer roller is a metal roller.
13. The method of claim 10, wherein said transfer roller is positioned distal from said printhead.
14. The method of claim 10, wherein said ink is subsequently transferred from said transfer roller onto a cleaning pad is in contact with said transfer roller.
15. The method of claim 14, wherein said transfer roller and said cleaning pad are substantially coextensive with said maintenance roller.
The claims below are in addition to those above.
All refrences to claim(s) which appear below refer to the numbering after this setence.
1. A computer-implemented method comprising:
identifying, for a retrieved webpage, script as a resource that is utilized by the webpage;
before attempting to download the script, checking a local cache for the script and any associated script profile data;
responsive to ascertaining that script profile data is present in the local cache, using the script profile data to compile the script.
2. The method of claim 1, wherein said identifying is performed by identifying a resource identifier associated with JavaScript.
3. The method of claim 1, wherein said identifying is performed by identifying a URL associated with JavaScript.
4. The method of claim 1, wherein the local cache comprises an HTTP cache in which other information associated with the webpage may be cached.
5. The method of claim 1, wherein said checking is performed by using a URL associated with JavaScript profile data.
6. The method of claim 1, wherein the profile data comprises JavaScript profile data associated with function usage.
7. The method of claim 1, wherein the profile data comprises JavaScript profile data associated with function call frequency.
8. The method of claim 1, wherein the profile data comprises JavaScript profile data associated with type hints for variables.
9. The method of claim 1, wherein the profile data comprises different classes of JavaScript profile data including: function usage, function call frequency, target function of call sites, type hints for variables, presence of implicit calls, array and element type, or function de-optimization hints.
10. One or more computer-readable storage media embodying computer readable instructions, which, when executed, implement a method comprising:
identifying, for a retrieved webpage, JavaScript as a resource that is utilized by the webpage;
before attempting to download the JavaScript, checking a local cache for the JavaScript and any associated JavaScript profile data;
responsive to ascertaining that JavaScript profile data is not present in the local cache, compiling the JavaScript;
creating JavaScript profile data associated with the JavaScript; and
caching the JavaScript and the JavaScript profile data in the local cache effective to enable JavaScript compilation in subsequent sessions that retrieve the same webpage or a different webpage that utilizes the same JavaScript.
11. The one or more computer-readable storage media of claim 10, wherein said creating comprises creating JavaScript profile data that is tailored to a device or a user’s interaction pattern.
12. The one or more computer-readable storage media of claim 10, wherein said checking is performed by using a URL associated with the JavaScript profile data.
13. The one or more computer-readable storage media of claim 10, wherein the JavaScript profile data comprises data associated with function usage.
14. The one or more computer-readable storage media of claim 10, wherein the JavaScript profile data comprises data associated with function call frequency.
15. The one or more computer-readable storage media of claim 10, wherein the JavaScript profile data comprises data associated with type hints for variables.
16. The one or more computer-readable storage media of claim 10, wherein the JavaScript profile data comprises different classes of profile data including: function usage, function call frequency, target function of call sites, type hints for variables, presence of implicit calls, array and element type, or function de-optimization hints.
17. A system comprising:
one or more computer readable storage media;
computer-readable instructions embodied on the one or more computer readable storage media which, when executed, implement a system comprising a JIT compiler configured to:
identify, for a retrieved webpage, JavaScript as a resource that is utilized by the webpage;
before attempting to download the JavaScript, check a local HTTP cache for the JavaScript and any associated JavaScript profile data;
responsive to ascertaining that JavaScript profile data is present in the local HTTP cache, use the JavaScript profile data to compile the JavaScript; and
responsive to ascertaining that the JavaScript profile data is not present in the local HTTP cache:
compile the JavaScript;
create JavaScript profile data associated with the JavaScript; and
cache the JavaScript and the JavaScript profile data in the local HTTP cache effective to enable JavaScript compilation in subsequent sessions that retrieve the same webpage or a different webpage that utilizes the same JavaScript.
18. The system of claim 17, wherein the JIT compiler is configured to create JavaScript profile data that is tailored to a device or a user’s interaction pattern.
19. The system of claim 17, wherein the JavaScript profile data comprises data associated with function usage.
20. The system of claim 17, wherein the JavaScript profile data comprises different classes of profile data including: function usage, function call frequency, target function of call sites, type hints for variables, presence of implicit calls, array and element type, or function de-optimization hints.