US20020023178A1

US20020023178A1 - Multiple-browser client architecture

Info

Publication number: US20020023178A1
Application number: US09/431,011
Authority: US
Inventors: Steven L. Strasnick; David Lundberg
Original assignee: ZAP ME! A Corp OF CALIFORNIA; Rstar Corp
Current assignee: Rstar Corp
Priority date: 1999-11-01
Filing date: 1999-11-01
Publication date: 2002-02-21
Anticipated expiration: 2019-11-01
Also published as: CA2359590A1; US6397264B1; EP1151373A1; WO2001033330A1; AU7589400A

Abstract

A method and apparatus for implementing a multiple-browser architecture is described. In one embodiment, the apparatus launches an application program in response to a trigger event. In addition, the apparatus maintains a history list corresponding to the launched application and allocates an application entity within an existing application window on the computer system. Further, the apparatus displays content data corresponding to the application program within the application window.

Description

FIELD OF THE INVENTION

The present invention relates to networked terminals that provide access to network resources. More particularly, this invention relates to a multiple-browser, multi-application client architecture.

BACKGROUND OF THE INVENTION

Efficient techniques for accessing and utilizing information are important considerations for manufacturers, designers and individual users of modern electronic information systems. Sources of such electronically available information include various types of electronic networks, such as the Internet, which are typically accessible through a compatible computer device or other similar electronic system.

Typical web browser programs (browser) run on the computer desktop as one of many applications. Control of the browser application window layout and management is performed by the underlying computer operating system (O/S). When additional functions, such as e-mail, are added to the browser, the additional functions are typically managed by the O/S as another window on the desktop.

Moving between the browser and application windows, such as word processing, is awkward as a new window is created for each and every application running on the system and interacts independently with the O/S. Newly created windows are easily lost or obscured by other windows. In addition, important features or information within underlying applications are not easily found.

In addition, other browser based functions such as e-mail, search, chat, and messaging appear in the browser as another web page causing awkward navigation between the functions. The foregoing leads to a loss of application state and context, disrupting the user's workflow.

SUMMARY OF THE INVENTION

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention is illustrated by way of example, and not by way of limitation in the figures of the accompanying drawings, in which like references indicate similar elements and in which: [0007]
FIG. 1 is a block diagram of one embodiment for a network configuration of a multiple-browser client architecture; [0008]
FIG. 2 is a block diagram of one embodiment for a network operations center of FIG. 1. [0009]
FIG. 3 is a block diagram of one embodiment for an architecture of a client; [0010]
FIG. 4 is a block diagram of one embodiment for a random accesses memory of FIG. 3; [0011]
FIG. 5 is a layout of one embodiment for a graphical user interface of a multiple-browser client architecture; and [0012]
FIG. 6 is a flow diagram of one embodiment for navigating a multiple-browser client architecture. [0013]

DETAILED DESCRIPTION

A method and apparatus for implementing a multiple-browser architecture is described. In one embodiment, an integrated desktop management system, optimized for multiple-browser, multi-application workflow is described. Key Internet and desktop functions such as e-mail, searching, chat, messaging, and the like exist within their own independently managed windows. Each function maintains its own state and navigation history. Navigational “click-throughs” from these functions to other web locations are automatically dispatched by a multiple-browser application to other browser window areas, allowing the user to preserve his or her place within each application. Third-party productivity applications, such as word processing, graphic programs and the like, may be integrated into and managed by the multiple-browser application to provide for efficient data exchange and context switching. All newly generated windows are managed by the multiple-browser application and are displayed within a content window on the display screen. This prevents critical interface functions from being obscured by the content window. [0014]
A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever. [0015]
In the following detailed description of the present invention, numerous specific details are set forth in order to provide a thorough understanding of the present invention. However, it will be apparent to one skilled in the art that the present invention may be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form, rather than in detail, in order to avoid obscuring the present invention. Although the description that follows describes the embodiments in terms of a web site, the embodiments are not so limited and may be practiced with any displayable information. [0016]
Some portions of the detailed descriptions which follow are presented in terms of algorithms and symbolic representations of operations on data bits within a computer memory. These algorithmic descriptions and representations are the means used by those skilled in the data processing arts to most effectively convey the substance of their work to others skilled in the art. An algorithm is here, and generally, conceived to be a self-consistent sequence of steps leading to a desired result. The steps are those requiring physical manipulations of physical quantities. Usually, though not necessarily, these quantities take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared, and otherwise manipulated. It has proven convenient at times, principally for reasons of common usage, to refer to these signals as bits, values, elements, symbols, characters, terms, numbers, or the like. [0017]
It should be borne in mind, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless specifically stated otherwise, throughout the following discussion, terms such as “processing” or “computing” or “calculating” or “determining” or “displaying” or the like refer to the action and processes of a computer system, or similar electronic computing device, that manipulates and transforms data represented as physical (electronic) quantities within the computer system's registers and memories into other data similarly represented as physical quantities within the computer system memories or registers or other such information storage, transmission or display devices. [0018]
The present invention also relates to apparatus for performing the operations herein. This apparatus may be specially constructed for the required purposes, or it may comprise a general purpose computer selectively activated or reconfigured by a computer program stored in the computer. Such a computer program may be stored in a computer readable storage medium, such as, but not limited to, any type of disk including floppy disks, optical disks, CD-ROMs, and magnetic-optical disks, read-only memories (ROMs), random access memories (RAMs), EPROMs, EEPROMs, magnetic or optical cards, or any type of media suitable for storing electronic instructions, and each coupled to a computer system bus. [0019]
The algorithms and displays presented herein are not inherently related to any particular computer or other apparatus. Various general purpose systems may be used with programs in accordance with the teachings herein, or it may prove convenient to construct more specialized apparatus to perform the required method steps. The required structure for a variety of these systems will appear from the description below. In addition, the present invention is not described with reference to any particular programming language. It will be appreciated that a variety of programming languages may be used to implement the teachings of the invention as described herein. [0020]
The present invention allows a user of a networked device, such as a computer system or a set-top box, to have access privileges based on user identity and the network device (e.g., terminal) used to access the network. In one embodiment, authorized users of the network have a user identity (e.g., login name and password) that identifies the user. Each authorized user of the network has a set of user privileges. The user privileges identify local resources (e.g., applications, media files) and network resources (e.g., World Wide Web pages, communications protocols, content channels) that are available to the user. In one embodiment, user access to particular applications, whether local or remote, are determined based on whether the user is current in access fees (i.e., billing status), if the resource is otherwise available to the user and the terminal being used. [0021]
In one embodiment, each device connected to the network has an associated set of device privileges that identify local resources and network resources that are provided by the device. When an authorized user of the network logs in at a terminal, that user is provided with session privileges that are the intersection of the individual user privileges and the device privileges of the device on which the user is logged in. Thus, a consistent, but not necessarily constant, set of access privileges can be provided to users regardless of the device used to access the individual resources. In other words, the user has access to all resources that the user has rights to, so long as those resources are available (based both on technical availability and usage policy) to the specific terminal being used regardless of the terminal being used and the location of the terminal. [0022]
FIG. 1 is a block diagram of one embodiment for a network configuration of a multiple-browser client architecture. The configuration of FIG. 1 is described in terms of both land-based communications and satellite communications; however, the manner of communication is not central to the present invention. Therefore, the present invention is applicable to any interconnection of devices that provide access to local and remote resources. [0023]
Referring to FIG. 1, wide area network (WAN) [0024] 100 provides an interconnection between local-area network 120, client 160, and network operations center 150. In alternate embodiments, any number of local-area networks 120, clients 160, and network operations center 150 may be connected to WAN 100. In one embodiment, WAN 100 is the Internet; however, any network or other interconnection may be used to implement wide area network 100.
In one embodiment, [0025] client 160 may be an individual terminal that provides access to network resources as well as local resources for a network user. In one embodiment, client 160 is a personal computer connected to wide area network 100 via a modem, a wireless connection, etc. In an alternate embodiment, client 160 may be a set-top box which may use a cable modem to access the WAN 100. In another embodiment, client 160 may be a “dumb” terminal, or a thin client device such as the ThinSTAR™ available from Network Computing Devices, Inc. of Mountain View, Calif.
Local-[0026] area network 120 provides an interconnection of devices at a local level. For example, local-area network 120 may interconnect multiple computers, printers, and other devices within one or more buildings. Local-area network 120 may be coupled to wide area network 100 or to satellite communications device 140. Local-area network 130 provides an interconnection of devices. In one embodiment, local-area network 120 contains a proxy server (not shown) for duplicating operations of network operations center 150.
[0027] Network operations center 150 is coupled to wide area network 100 and provides access to network resources for client 160 and local-area network 120. Network communications center 150 communicates via wide are network 100 with either client 160 or local-area network 120. Network operations center 150 and local-area network 120 may communicate via wide area network 100 and/or satellite communications devices 140.
In one embodiment, [0028] network operations center 150 includes multiple servers (not shown in FIG. 1) that provide access to network and other resources. For example, network operations center 150 may include a Web proxy server that provides access to the World Wide Web (WWW, or the Web) for devices of local-area network 120, and client 160. Network operations center 150 may also include other devices, such as, for example, a middleware server or a file server, that provide information to devices coupled to network operations center 150.
In one embodiment, information is communicated between [0029] network operations center 150 and local-area network 120 via satellite communications devices 140. Satellite communications devices 140 includes the necessary components to provide communications between network operations center 150 and local-area network 120. In one embodiment, satellite communications may be accomplished using Transmission Control Protocol/Internet Protocol (TCP/IP) embedded within a Digital Video Broadcast (DVB) stream. In alternate embodiments, any well-known communication protocol can be used. In one embodiment, satellite communications are bi-directional. Alternatively, if satellite communications are uni-directional, wide area network 100 may be used to provide a hybrid asymmetrical bi-directional communications system, such as the SkySurfer™ platform available from Gilat Satellite Networks, Inc. of McLean, Va.
FIG. 2 is a block diagram of one embodiment for a [0030] network operations center 150. With respect to description of FIG. 2, wide area network 100 and satellite communications devices 140 are implemented as described above in FIG. 1. Notwithstanding being described as including certain types of servers and other devices, network operations center 150 may include different or additional components as well as multiple components, for example, multiple Web servers. Each server may be composed of one or more software and/or hardware components.
Network operations center (NOC) [0031] 150 provides resources to local-area networks and individual clients (not shown). In addition, in one embodiment, NOC 150 may provide a gateway to a larger network such as, for example, the Internet. Thus, network operations center 150 may be used to provide a controlled set of resources while being part of a larger network. This is particularly advantageous in situations where users of the local-area networks are somewhat homogenous. For example, students in similar grade levels, professionals, and other groups.
Additional uses and details of network operations center configuration can be found in U.S. patent application Ser. No. 09/XXX,XXX (P001), entitled “OPTIMIZING BANDWIDTH CONSUMPTION FOR DOCUMENT DISTRIBUTION OVER A MULTICAST ENABLED WIDE AREA NETWORK” and U.S. patent application Ser.No. 09/XXX,XXX (P002), entitled “A METHOD AND APPARATUS FOR SUPPORTING A MULTICAST RESPONSE TO A UNICAST REQUEST FOR DATA,” both of which are assigned to the corporate assignee of the present invention. [0032]
Referring again to FIG. 1, [0033] NOC router 200 is coupled to NOC LAN 205 and provides routing and firewall functionality for the servers and other components of network operations center 150. NOC router 200 may be implemented in any manner known in the art. In one embodiment, database 260 is coupled to NOC LAN 205. Database 260 may be used, for example, to store information about authorized users of associated local-area networks, or to store information about resources that are available on each terminal connected to the network. Database 260 may also be used to store statistics about network usage, advertisements to be downloaded to devices of the local-area networks, etc. Data 265 represents data stored by database 260 and may be one or more physical devices.
[0034] Master proxy server 270 is also coupled to NOC LAN 205 to provide World Wide Web resources to devices of the connected local-area network(s) or individual clients. In one embodiment, web server 210 is a Hypertext Markup Language (HTML) and/or Secure Sockets Layer (SSL) server. In alternate embodiments, Web server 210 may be any other suitable server. Web cache 220 is used to store Web resources (e.g., Web pages) that are most often accessed, most recently accessed, etc. In one embodiment, Web cache 220 stores a predetermined set of Web resources that are provided to the local-area networks. For example, in a school network environment, the cached Web resources may be a pre-approved set of Web pages. In one embodiment, all or a portion of the contents of Web cache 220 are replicated on local networks.
[0035] Middleware server 230 manages database applications in network operations center 150. For example, middleware server 230 may determine which users have access to Web server 210. By querying the user database, middleware server 230 acts as an interface between clients and servers as well as between servers. Alternatively, each client and server may act as its own middleware device by interfacing with the database servers on their own behalf though existing database interfacing technologies such as the Common Object Request Broker Architecture (CORBA) as defined by Object Management Group, Inc. of Framingham, Mass. or COM+ available from Microsoft Corporation of Richmond, Wash.
[0036] Application server 240 provides applications programs to devices coupled to network operations center 150. For example, application server 240 may provide HTML-formatted e-mail services to one or more devices. Application server 240 may also run and manage run-time applications on clients 160 connected local-area networks.
FIG. 3 is a block diagram of one embodiment for an architecture of a [0037] client 160. Referring to FIG. 3, CPU 302 is coupled via a bus 315 to a variety of memory structures and input/output 310. The memory structures may include read only memory (ROM) 304, random access memory (RAM) 306, and/or non-volatile memory 308. In one embodiment, CPU 302 is also coupled via bus 315 to a network interface 312. Network interface 312 is used to communicate between client 160 and network operations center 150 and a variety of other clients 160. Network interface 312 is coupled to the wide area network 100 or to local-area network 120 by any of a variety of means such as, for example, a telephone connection via modem, a DSL line, or the like.
FIG. 4 is a block diagram of one embodiment for random access memory (RAM) [0038] 306. Referring to FIG. 4, RAM 306 contains multiple-browser application 402, client configuration 404, multiple-browser windows cache 406, and history list 408. In one embodiment, history list 408 contains history list 1 (410) through history list n (420). Multiple-browser application 402 communicates with network operations center 150 or with a proxy server maintained within local-area network 120 to manage the multiple browsers and applications accessed by the user. All navigation between windows applications and web applications is controlled by multiple-browser application 402. Client configuration 404 contains information to allow a user to sign-on to the system and to configure client 160. Client configuration 404 may contain user identification and/or passwords for sign-on and a configuration profile for specifically allowing access to various applications and web pages maintained on client 160, network operations center 150, and/or local-area network 120.
Multiple-[0039] browser windows cache 406 contains a number of content windows accessed by the user. As the user navigates within the system, various areas of the system are opened and displayed in specific windows on the desktop. The content of the window accessed or displayed by the system is maintained in the cache 406. For example, web pages accessed through a web browser program are opened within a browser window. Each web page content is cached in multiple-browser windows cache 406. In one embodiment, multiple-browser application 402 may open application, media, content, browser, and other windows and save the content of the pages accessed for each of these types of windows in cache 406. In one embodiment, the content for each window may be maintained in separate areas within the cache 406. In an alternate embodiment, individual caches may be maintained for the individual windows.
A [0040] history list 408 is maintained for each of the windows supported by the client configuration 404. In one embodiment, each history list 408 may contain an entry indicating the page of information displayed, the window it came from, and the location of the content in cache 406. In an alternate embodiment, any suitable information may be maintained. In one embodiment, a history list 408 may be maintained for each window type stored in multiple-browser windows cache 406. In addition, a separate history list 408 may be maintained for each application accessed within each window. For example, a history list 408 may be maintained for access to a browser, a chat room, and application tools. Application tools may consist of a number of local applications such as, for example, word processing, graphics programs, and multi-media programs. The local applications are maintained on and processed by client 160. In one embodiment, a separate history list 408 may be maintained for the browser, chat room, and for each of the application programs within the application tools. In one embodiment, an entry for each application accessed under application tools may be entered into a browser bookmark file.
After the user has signed-on to the system, multiple-[0041] browser application 402 configures the client 160 based upon information within client configuration 404 in order that the user may access a variety of applications (such as, for example, a browser, chat, and the applications within application tools). As the user navigates within a given application, the pages or windows of the application are displayed within a main content window on the display screen and the content of each page is saved in cache 406. In addition, an entry is entered into the appropriate history list 408 for the application. The user may move between the various applications by manipulating or “clicking” navigation buttons on the desktop. Whenever the user navigates back to a previously accessed application, multiple-browser application 402 accesses the history list 408 for the application, retrieves the content for the history list 408 entry from cache 406, and displays the content within the content window. Thus, the system provides an integrated, webcentric desktop management system that seamlessly manages the state of each application active within the system and allows the user to move effortlessly from one application to another.
FIG. 5 is a layout of one embodiment for a graphical user interface (GUI) [0042] 500 of a multiple-browser client architecture. In one embodiment, GUI 500 is displayed upon client 160 and is configured based on pre-defined user privileges and the terminal privileges. In one embodiment, GUI 500 provides the gateway by which a user accesses both local and remote resources. Thus, the configuration of GUI 500 determines the resources to which the user has access.
In one embodiment, [0043] navigation buttons 502 provide graphical “buttons” that allow a user to perform certain operations. Navigation buttons 502 may include, for example, “back,” “forward,” and “stop” buttons for browser control as well as “save,” “open,” and “print” buttons for general application control. In alternate embodiments, fewer, and/or different buttons and commands may be included in navigation buttons 502 (e.g. the ability to type in a URL, history navigation button, and bookmark button).
In one embodiment, applications/[0044] edit menus 506 provides application selection control and general editing control for multiple applications within content window 508. For example, applications/edit menus 506 may include a list of all local and/or remote applications available to the user of the terminal on which GUI 500 is displayed. For example, from the tools menu, the user may select an application to use. The edit portion provides general editing commands such as “cut,” “copy,” and “paste” for the user to move data between available applications.
In one embodiment, points [0045] meter 504 provides a summary of incentive points or other points schemes available to the user. An incentive points management scheme is described in greater detail in U.S. patent application Ser.No. 09/XXX,XXX (P004) entitled “METHOD AND APPARATUS FOR INCENTIVE POINTS MANAGEMENT,” which is assigned to the corporate assignee of the present invention.
[0046] Content window 508 provides space for the user to interact with the resources accessed. For example, if a word processing application is being accessed, content window 508 displays the word processing application within content window 508 when the application is activated. The user may switch between applications and move data between applications that are available on the terminal using applications/edit menus 506 should the current user have sufficient privileges to do so on the current terminal. If a browser application is being used, content window 508 is used to display a browser window.
In one embodiment, feature and [0047] channel buttons 510 provide access to features (e.g., e-mail, chat rooms, message boards, bookmarks) and channels (e.g., educational topics, news topics) available to the user. Feature and channel buttons 510 are configured based on the session privileges such that only the features and channels available to or associated with the user appear. Feature and channel buttons may also control what is displayed in content window 508.
In one embodiment, [0048] dynamic billboard 512 provides advertising and/or other information to the user while the user is using an application or browser. One embodiment of an advertising implementation for dynamic billboard 512 is disclosed in U.S. patent application Ser.No. 09/XXX,XXX (P003) entitled “MICRO-TARGETED DIRECT ADVERTISING,” which is assigned to the corporate assignee of the present invention. In alternate embodiments, dynamic billboard 512 may be used for other purposes such as, for example, video conferencing, instant messaging, distance learning/instruction, news updates, or other uses.
In one embodiment, [0049] messaging windows 514 display messages to the user. For example, an instructor may send messages to students, a user of one terminal may send a message to a user of another terminal, a system administrator may send messages to a user or a group of users, or the system may send a notification that the user has received e-mail. Messaging windows 514 are used for messages that are independent of content window 508, so long as such messages are allowed by the current session privileges.
FIG. 6 is a flow diagram of one embodiment for navigating a multiple-browser client architecture. Initially at [0050] processing block 604, a user signs-on to the system. In one embodiment, the user signs on using a user identification and password combination. After the user's sign-on is verified, client 160 is configured for the particular identification/password combination. Configuration settings are maintained in client configuration 404 and allow or deny access to a number of applications maintained on network operations center 150 and/or client 160. In addition, applications may be maintained on a proxy server located within local-area network 120. In one embodiment, applications comprise browser, chat, e-mail, advertisements, network operations center content, and client applications. Client applications are application programs maintained on client 160 such as, for example, word processing, graphics programs, educational programs, and the like.
After the user signs-on and the configuration is set, multiple-[0051] browser application 402 waits for user input at processing block 608. If at processing block 608, the user launches an application, processing continues at processing block 612. In one embodiment, the user may launch an application by accessing a feature or navigation button 502 or accessing an application through an application tools menu 506. At processing block 612, the chosen application is launched and the history list 408 for the application is updated. If the history list 408 for the application does not exist, a new history list is created. At processing block 616, the content page for the application is displayed within content window 508 and the content is cached in multiple-browser windows cache 406. In an alternate embodiment, the content may not be cached until the user navigates to another page of information.
At [0052] processing block 620, multiple-browser application 402 determines if another application has been launched. As above, the application may be launched by a variety of methods. If another application has been launched, processing returns to processing block 612. If another application has not been launched, multiple-browser application 402 determines if a navigation button 502 for the particular application has been accessed. If a navigation button 502 has been accessed, processing returns to block 612. If a navigation button 502 has not been accessed, processing returns to block 620.
The user may launch applications by a variety of methods. For example, the user may launch the chat or e-mail applications by clicking on a feature or [0053] channel button 510 on the desktop. The user may access a web page for the sponsor of an advertisement by clicking on the advertisement dynamic billboard 512. For example, if the user clicks on the dynamic billboard 512, the browser application is accessed and the web site of the sponsor is displayed within content window 508. In one embodiment, the content is cached in a media window cache within multiple-browser windows cache 406 and a history list 408 entry is made for the window.
The invention has been described in conjunction with the preferred embodiment. It is evident that numerous alternatives, modifications, variations and uses will be apparent to those skilled in the art in light of the foregoing description. [0054]

Claims

What is claimed is:

1. A method of implementing a multiple-browser client architecture within a computer system, the method comprising:

launching an application program in response to a trigger event;

maintaining a history list corresponding to the launched application;

allocating an application entity within an existing application window on the computer system; and

displaying content data corresponding to the application program within the application window.

2. The method of claim 1 further comprising:

caching the content data within a content cache.

3. The method of claim 1 wherein the history list comprises a plurality of entries, each of said entries indicating the application the content data came from, a pointer to an application window the content data came from, and a location of the content.

4. The method of claim 1 wherein displaying further comprises:

locating one of an existing application entities; and

inserting content data corresponding to the application program within the one existing application entity.

5. The method of claim 1 wherein launching, maintaining, allocating, and displaying are repeated for a plurality of applications, each of said plurality of applications having a corresponding history list.

6. The method of claim 1 further comprising:

determining if a new trigger event has occurred;

if a new trigger event has occurred, launching a second application program, maintaining a second history list corresponding to the second application, allocating a second application entity within an existing application window, and displaying content data corresponding to the second application program within the existing application window.

7. The method of claim 1 further comprising:

receiving data from a server; and

allocating the data within pre-defined windows on the computer system.

8. The method of claim 7 wherein a new history list is maintained for the data.

9. The method of claim 1 wherein the trigger event is selected from the group consisting of accessing a feature button, accessing a navigation button, clicking on an application window, and accessing an application menu.

10. A system for implementing a multiple-browser client architecture within a computer system, the system comprising:

means for launching an application program in response to a trigger event;

means for maintaining a history list corresponding to the launched application;

means for allocating an application entity within an existing application window on the computer system; and

means for displaying content data corresponding to the application program within the application window.

11. The system of claim 10 further comprising:

means for caching the content data within a content cache.

12. The system of claim 10 wherein means for displaying further comprises:

means for locating one of an existing application entities; and

means for inserting content data corresponding to the application program within the one existing application entity.

13. The system of claim 10 wherein the means for launching, means for maintaining, means for allocating, and means for displaying are repeated for a plurality of applications, each of said plurality of applications having a corresponding history list.

14. The system of claim 10 further comprising:

means for determining if a new trigger event has occurred;

if a new trigger event has occurred, means for launching a second application program, means for maintaining a second history list corresponding to the second application, means for allocating a second application entity within an existing application window, and means for displaying content data corresponding to the second application program within the existing application window.

15. The system of claim 10 further comprising:

means for receiving data from a server; and

means for allocating the data within pre-defined windows on the computer system.

16. An article of manufacture having one or more computer-readable medium with executable instructions therein, which when executed by a processing device causes the processing device to:

launch an application program in response to a trigger event;

maintain a history list corresponding to the launched application;

allocate an application entity within an existing application window on the computer system; and

display content data corresponding to the application program within the application window.

17. The medium of claim 16 further configured to:

cache the content data within a content cache.

18. The medium of claim 16 wherein displaying further comprises:

locate one of an existing application entities; and

insert content data corresponding to the application program within the one existing application entity.

19. The medium of claim 16 wherein the launching, maintaining, allocating, and displaying are repeated for a plurality of applications, each of said plurality of applications having a corresponding history list.

20. The medium of claim 16 further configured to:

determine if a new trigger event has occurred;

if a new trigger event has occurred, launch a second application program, maintain a second history list corresponding to the second application, allocate a second application entity within an existing application window, and display content data corresponding to the second application program within the existing application window.

21. The medium of claim 16 further configured to:

receive data from a server; and

allocate the data within pre-defined windows on the computer system.

22. A system for implementing a multiple-browser client architecture within a computer system, the system comprising:

a multiple-browser application configured to launch an application program in response to a trigger event; and

a history list, corresponding to the application program, wherein the multiple-browser application is configured to allocate the application program within a content window on the computer system, and to display content data corresponding to the application program within the application window.

23. The system of claim 22 further comprising:

a content cache for maintaining the content data from the application program.

24. The system of claim 22 wherein the history list comprises a plurality of entries, each of said entries indicating the application the content data came from, a pointer to an application window the content data came from, and a location of the content.

25. The system of claim 22 wherein the multiple-browser application is configured to launch a plurality of application programs.

26. The system of claim 25 wherein a plurality of history lists are maintained, wherein each of said plurality of history lists corresponds to each of said plurality of program applications.

27. The system of claim 22 further comprising:

a plurality of pre-defined windows on the computer system, wherein data received from a server is allocated within the pre-defined windows.

28. The system of claim 27 wherein a new history list is maintained for the data.

29. The system of claim 22 wherein the trigger event is selected from the group consisting of accessing a feature button, accessing a navigation button, clicking on an application window, and accessing an application menu.

30. A computer system comprising:

a bus;

a processor, coupled to the bus; and

a memory device, coupled to the bus, comprising

a multiple-browser application configured to launch an application program in response to a trigger event, to allocate an application entity within an existing application window on the computer system, and to display content data corresponding to the application program within the application window, and

a history list, corresponding to the application program, configured to maintain a plurality of entries, each of said entries indicating the application the content data came from, a pointer to an application window the content data came from, and a location of the content.