1808 results about "JavaScript" patented technology

Protection systems and methods provide for protecting one or more personal computers (“PCs”) and / or other intermittently or persistently network accessible devices or processes from undesirable or otherwise malicious operations of Java™ applets, ActiveX™ controls, JavaScript™ scripts, Visual Basic scripts, add-ins, downloaded / uploaded programs or other “Downloadables” or “mobile code” in whole or part. A protection engine embodiment provides, within a server, firewall or other suitable “re-communicator,” for monitoring information received by the communicator, determining whether received information does or is likely to include executable code, and if so, causes mobile protection code (MPC) to be transferred to and rendered operable within a destination device of the received information, more suitably by forming a protection agent including the MPC, protection policies and a detected-Downloadable. An MPC embodiment further provides, within a Downloadable-destination, for initiating the Downloadable, enabling malicious Downloadable operation attempts to be received by the MPC, and causing (predetermined) corresponding operations to be executed in response to the attempts, more suitably in conjunction with protection policies.

A process is disclosed for using the existing Universal Resource Identifier (URI) history feature of browsers to maintain user preference settings, or other state information, used by one or more web sites or other systems. In one embodiment, when a user makes a particular preference selection on a web site, the user's selection is recorded in the browser's URI history by causing the browser to access a URI (or a set of URIs) representing the particular selection. The same or a different web site may subsequently test the browser's URI history for this particular URI by including appropriate JavaScript or other executable code in a page requested by the browser. Depending upon the outcome of this test, the web site and / or the page's executable code may take an appropriate action or inaction consistent with the preference selection.

Several different embodiments of an electronic document delivery system are described including a client machine (e.g., a palmtop / handheld computer or wireless communication device) coupled to a transcoder proxy. One embodiment of the system allows a client machine with limited resources to support JAVASCRIPT. The transcoder proxy receives an electronic document in a first digital format (e.g., HTML or XML). A JAVASCRIPT event may be associated with an element of the document including JAVASCRIPT code executed in response to the JAVASCRIPT event. The transcoder proxy assigns a unique identifier to the element, and forms a model of a logical structure of the document (e.g., a document object model or DOM). The transcoder proxy uses the model to produce an “original” script including a portion of the document expressed in a second digital format (e.g., a scripting language), and provides the original script to the client machine. The client machine uses the original script to display / present the document portion. The client machine associates the JAVASCRIPT event with the element identifier, generates the JAVASCRIPT event in response to user input, and provides JAVASCRIPT event information and the associated identifier to the transcoder proxy. The transcoder proxy accesses the element within the model using the identifier, executes the JAVASCRIPT code producing a result, uses the model and the result to produce a “modification” script, and provides the modification script to the client machine. The client machine uses the modification script to modify the displayed / presented portion of the document.