Browse Prior Art Database

An Appparatus for piping form- based on the web Disclosure Number: IPCOM000014983D
Original Publication Date: 2001-Jul-04
Included in the Prior Art Database: 2003-Jun-20
Document File: 2 page(s) / 48K

Publishing Venue




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

Page 1 of 2

An Appparatus for piping form- based on the web


    More and more Web applications allow users to post-process other form-based Web applications for enriched results. Let's refer to the Web application that does the post-processing as the "parasite application," and to the application that is post-processed as the "original application." In general, the parasite application typically modifies the original application's form and directs its actions (such as a CGI script call) to the parasite application. The parasite application is then in charge of interacting with the original application. In such an approach, the parasite application must be aware of the format of the original form and can "parasite" only a finite set of original applications.

    In this disclosure, we propose an apparatus that does not require the parasite application to know what the format of the original form is, and that allows the user to specify interactively the URL of any original application, remotely operate it and post-process it, whatever its syntax is, as long as the apparatus is semantically consistent in combining the two applications.


    An apparatus for "piping" (by analogy with the Unix piping mechanism) a parasite application with one or more form-based Web services, in a way that does not require the parasite application to "understand," or even to be aware of, the format of the original application(s).


  The basic principle of this disclosure consists of "piping" the parasite application with the original application as follows:

    The user accesses the parasite application form (for instance, an application that adds any URL to the browser's bookmarks).

    The user dynamically enters in that form a pointer (URL) to any form-based original application, for which the post-processing makes sense (for instance, a search service), and possibly enters some parameters into the parasite application form.

    The parasite application fet...