Browse Prior Art Database

A system and method to detect and prevent “mistakenly executed requests” at request-originating-node or an intermediate node.

IP.com Disclosure Number: IPCOM000182630D
Original Publication Date: 2009-May-05
Included in the Prior Art Database: 2009-May-05
Document File: 6 page(s) / 131K

Publishing Venue

IBM

Abstract

Many a times, by mistake, user clicks on links, buttons or menu options like logout, submit, go, finish, etc. which goes to the application for execution. Generally, applications ask “Proceed Confirmation” from user by prompting messages like “Are you sure?”, “Confirm”, etc. However, not all applications are aware of user behavior/pattern of using the application. Moreover, user often unintentionally makes requests to application by involuntarily pressing “Enter Key”, “Esc Key”, “Spacebar Key”, “Mouse Button”, etc. which the application may not prompt for confirmation. A system and method are proposed which allows users to stop the execution of such mistakenly executed requests.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 40% of the total text.

Page 1 of 6

A system and method to detect and prevent "mistakenly executed requests" at request-originating-node or an intermediate node.

     Author Jaikumar N Kawale

1. Title:

A system and method to detect and prevent "mistakenly executed requests" at request-originating-node or an intermediate node are disclosed.

2. Problem Description:

Many a times, by mistake, user clicks on links, buttons or menu options like logout, submit, go, finish, etc. which goes to the application for execution. Generally, applications ask "Proceed Confirmation" from user by prompting messages like "Are you sure?", "Confirm", etc. However, not all applications are aware of user behavior/

p

                            attern of using the application. Moreover, user often unintentionally makes requests to application by involuntarily pressing "Enter Key", "Esc Key", "Spacebar Key", "Mouse Button", etc. which the application may not prompt for confirmation. A system and method are proposed which allows users to stop the execution of such mistakenly executed requests.

3. Solution Outline:

In the proposed system, each request of user is passed on to a proposed hold-request-software to determine whether the request should be passed on to the application for execution. The hold-request-software maintains a set of parameters defining mistakenly executed requests by the user. These parameters can be customized by having inputs from user, application-in-concern via metadata, other applications, web services, user machine configuration, etc. The initial set of

p

 arameters can be created for the most likely mistakenly executed requests like logout, submit, go, etc. The hold-request-software can continuously update these parameters internally by analyzing each request from the user. The hold-request-software is executed at request-origination-node. In case of distributed applications, hold-request-software can also be executed on an intermediate node in the network before forwarding the request to the node where the application is running. The novelty is in the fact that the detection and prevention

p

 rocess doesn't need to be executed on the node running application, e.g. the application server. It is also a novelty of this invention that the proposed hold-request-software can detect and

p

revent the mistakenly executed requests in a standalone application as well. Moreover, a novel

system and method is proposed to detect and prevent the mistakenly executed requests.

4. Solution Description:

Instead of relying on the applications to handle user confirmation on his/her requests, the hold-request-software acts as an intermediate between the user requests and the application to get user request confirmation. The hold-request-software can be embedded as a plug-in in internet browser for intercepting all requests of client in web based applications. For desktop applications, it can be an event handler that the application calls. Application Programming Interfaces (APIs) o...