Remote invocation mechanism for logging
One or more events occurring within a client-side web application are logged at a remote server using a script-based invocation mechanism. The mechanism comprises a client-side script, and associated server-side code. Upon occurrence of an event to be logged, a script object is created on the client and used to pass logged data to the server, which then issues a response to destroy the script object. In this manner, the script object is created and persists in the client only as long as it is needed to log the event.
1. A method operative in a client having a web browser that renders a markup language page, comprising: receiving the markup language page in the web browser; upon occurrence of an event, dynamically creating and inserting a script object into the markup language page, the script object being a distinct set of instructions, wherein the script object is not present in the markup language page when the markup language page is received in the web browser; executing the script object to collect data concerning the event and to forward that data to a server, wherein the data describes one of: a feature, a fault, and a failure; and upon receipt of a response from the server, destroying the script object by removing the set of instructions from the markup language page.
2. The method as described in claim 1 wherein the response from the server is a delete script that is written into the markup language page.
3. The method as described in claim 2 wherein the delete script causes the script object to be deleted from the markup language page after a given timeout.
4. The method as described in claim 1 wherein the event is an action associated with a given markup language page object.
5. The method as described in claim 1 wherein the data is forwarded to the server via http.
6. The method as described in claim 1 wherein the server is operated within a managed service.
7. The method as described in claim 1 wherein the script object is a Javascript object.
8. Apparatus, comprising: a tracking server executed by a processor; and a control script integrated into a markup language page and adapted to be executed by a client browser upon a given occurrence, wherein, upon such execution, the control script (a) dynamically creates and inserts a script object into the markup language page, the script object being a distinct set of instructions that collects and forwards to the server data about the given occurrence, the data being log data that describes one of: a feature, a fault, a failure, and an event, and (b) upon receipt of a response from the server, removes the script object from the markup language page by removing the set of instructions from the markup language page; wherein the script object is not present in the markup language page when the markup language page is received in the web browser.
9. The apparatus as described in claim 8 wherein the response from the server comprises a delete script that the control script writes into the script object to cause the script object to be removed from the markup language page.
10. The apparatus as described in claim 8 wherein the markup language page is associated with a web application, or a Rich Internet Application.
11. A system, comprising: a tracking server executed by a processor; and a script integrated into an application and adapted to be executed upon a given occurrence, wherein, upon such execution, the script (a) dynamically creates and inserts a script object into the application, the script object being a distinct set of instructions that collects and forwards to the server data about the given occurrence, wherein the given occurrence is one of: a feature execution, a feature failure, and a feature fault, and (b) upon receipt of a response from the server, destroys the script object by removing the set of instructions from the markup language page; wherein the script object is not present in the markup language page when the markup language page is received in the web browser; wherein the application is available at a set of client browsers across a network.
12. The system as described in claim 11 wherein the application is a web page having a browser-enabled script, or a Rich Internet Application.