US20020013804A1 - Event management in a system with application and graphical user interface processing adapted to display predefined graphical elements resides separately on server and client machine - Google Patents
Event management in a system with application and graphical user interface processing adapted to display predefined graphical elements resides separately on server and client machine Download PDFInfo
- Publication number
- US20020013804A1 US20020013804A1 US09/164,244 US16424498A US2002013804A1 US 20020013804 A1 US20020013804 A1 US 20020013804A1 US 16424498 A US16424498 A US 16424498A US 2002013804 A1 US2002013804 A1 US 2002013804A1
- Authority
- US
- United States
- Prior art keywords
- server
- client machine
- events
- application
- user interface
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/542—Event management; Broadcasting; Multicasting; Notifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/451—Execution arrangements for user interfaces
- G06F9/452—Remote windowing, e.g. X-Window System, desktop virtualisation
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/133—Protocols for remote procedure calls [RPC]
Definitions
- the present invention relates generally to client-server processing and, more particularly, to an application environment wherein application logic and business rules reside on a server to which users attach from client machines that have independent graphical user interface (GUI) processing.
- GUI graphical user interface
- GUI Graphical User Interface
- World Wide Web the graphical side of the Internet
- Some operating systems such as the Windows operating system
- use an event queue to process and sequence events such as key strokes, mouse clicks, etc.
- sequence events such as key strokes, mouse clicks, etc.
- events such as key strokes are simply delivered to the window that is currently active. This, however, becomes somewhat complicated if a key stroke is able to activate another window. As fast users often type ahead, there is no assurance that key strokes will be sent to the intended window.
- a primary object of the present invention is to provide a network-based system that allows for high speed data entry at a remote client.
- a further object of the invention is to provide a network-based system for remote data processing in which substantially all application logic and business rules reside on a common server, and GUI processing is performed separately at a client machine.
- a further object of the invention is to provide a network-based system providing a sophisticated user interface at a client machine controlled by a server using a low bandwidth connection (such as a 28.8 kbps modem connection) and minimal client resources.
- a low bandwidth connection such as a 28.8 kbps modem connection
- Another object of the invention is to provide a network-based system for remote data processing that is scaleable to a large number, e.g., hundreds, of concurrent users.
- a network-based system in which application logic and business rules reside on a server to which a user attaches from a client machine.
- the system includes a view manager residing on the client machine for generating a graphical user interface (GUI) environment for the user.
- An application engine resides on the server for controlling the view manager. Events in an event queue at the client machine are parsed to determine which events require application processing. Events requiring application processing are sent to the server and other events are left in the event queue.
- the system also maintains stack synchronization between the client machine and the server.
- the inventive system allows remote high speed data entry while maintaining keystroke synchronization.
- the system is scaleable to a large number, e.g., hundreds, of concurrent users. It provides a sophisticated user interface at the client machine controlled by the server using a low bandwidth connection (such as a 28.8 kbps modem connection) and minimal client resources.
- FIG. 1 shows an illustrative network environment in which the inventive system is implemented
- FIG. 2 is a simplified block diagram of the system
- FIG. 3 is a block diagram illustrating idealized keystroke processing
- FIG. 4 is a block diagram illustrating the effects of network delay in keystroke processing.
- FIG. 5 is a flow chart illustrating the event loop system in accordance with the present invention.
- FIG. 1 A representative client-server network environment in which the present invention can be implemented is illustrated in FIG. 1.
- a client machine 10 is connected to an application server platform 12 via network 14 .
- the network 14 can be the Internet, an Intranet or other network connection. It preferably comprises the Internet's World Wide Web, making information accessible remotely using view manager software.
- Application server platform 12 is one of a plurality of servers that are accessible by the clients, one of which is illustrated by the machine 10 .
- the client machine 10 includes a processor 11 , an operating system 13 , a graphical user interface 15 , and a View Manager 16 .
- a representative application server platform 12 comprises a processor 18 such as, e.g., an IBM RISC System/6000 computer (a reduced instruction set or so-called RISC-based workstation) running an Operating System 20 such as, e.g., the Windows NT Operating System.
- the platform 12 also includes an application server program 22 .
- the platform 12 also preferably includes a graphical user interface (GUI) 24 for management and administration.
- the application server 22 includes an Application Programming Interface (API) 23 that provides extensions enabling application developers to extend and/or customize the core functionality.
- API Application Programming Interface
- a representative client is a personal computer (PC) workstation that is x86-, PowerPC®- or RISC-based, that includes an operating system such as Microsoft Windows 3.1 and Windows 95 (or higher), and that includes the View Manager 16 .
- PC personal computer
- substantially all application logic and business rules reside on the common Windows NT server 12 .
- the client 10 preferably comprises a so-called thin client (with minimal client resources) having full Graphical User Interface (GUI) functionality, but containing substantially no application level intelligence.
- GUI Graphical User Interface
- the thin client 10 is capable of performing well using a 28.8 modem connection through the Internet.
- the inventive system is scaleable to large numbers, e.g., hundreds of concurrent users.
- the normal Windows components are separated into two distinct objects: the data model (which contains substantially all of the information about an object such as color, size, font, position, etc.) and the View Manager (which uses information from the data model to construct an actual GUI element).
- the data model resides on the server, and the View Manager resides on the client machine.
- the system includes a message passing architecture that allows the data model and the View Manager to communicate with each other.
- the View Manager uses information from the data model (obtained from a message) to construct a GUI element, and then sends messages to the data model if the user changes any of the view characteristics. These messages can be sent locally or over any TCP/IP connection.
- FIG. 2 is a simplified block diagram illustrating system components in greater detail.
- the underlying architecture is based on an n-tier paradigm using a message passing IPC (InterProcess Communications) protocol.
- Each tier in the system is composed of one or more processes referred to as Managers.
- the View Manager 16 is responsible for rendering graphical elements, interfacing with the user, and forwarding events to the server 12 .
- the Forms Manager 32 (using the data model) provides the control structures that manage the View Manager objects, respond to events, and interface with the application layer to provide program flow control. While the Forms Manager 32 controls the GUI elements on the View Manager 16 , it preferably has no actual GUI elements itself.
- the system is composed of three basic components: a remote object client 10 , a remote object server 12 , and a dispatcher 14 .
- the objects communicate with each other by sending messages.
- a message is a packet of bytes passed from one object to another. There is no predefined structure to a message except that defined by the sending and receiving objects.
- the dispatcher preferably uses a simple message passing structure based on the Winsock/Berkeley sockets TCP/IP interface to communicate between objects. Parameters are placed directly into a message buffer. The message is sent via the dispatcher to the remote system using standard TCP/IP socket calls. It is then passed to the target object. The arguments are removed from the message and the appropriate code is called to perform the function.
- a flag indicates if a response is required to the message. Not only does this approach simplify the steps needed to build the application, but it gives us complete control over the underlying communications parameters and requires no specialized software to be installed on the client or the server.
- the client and server components at this lowest level are responsible for routing a message received from the dispatcher to the appropriate object.
- the View Manager 16 implements only the client component preferably using Windows Asynchronous Sockets to allow it to run in the Windows 3.1 and Windows 95 environments.
- the server software implements both the server and the client components in a multi-threaded environment preferably using a standard Berkeley sockets style interface. By implementing both server and client components, the server process can function as both a server for the View Manager 16 , and as a client to other processes. This provides the foundation for the n-tier architecture.
- the Forms Management layer allows GUI elements to be created and controlled by the server 12 on a remote client 10 .
- the server can control sophisticated user interfaces using a low bandwidth connection and minimal client resources.
- the Forms Manager 32 Layered on top of the Forms Manager 32 is a Database Manager 34 designed to provide relational database access to information, and Application Specific Code 36 that provides the business rules and program control logic. Both of these layers execute in the multi-threaded server process and have full access to the communications layer. This provides the core functionality of the system.
- the View Manager 16 is a relatively small, simple Windows application that requires virtually no specialized client software aside from a standard TCP/IP interface.
- the server components provide all application control logic and business rules. Together they form a very powerful framework to provide sophisticated GUI applications that can run over low bandwidth communication links.
- the View Manager 30 which resides on the client workstation 10 , provides a full GUI environment and communicates with the Forms Manager 32 through a message architecture. It is responsible for all user input processing and output rendering. As will be described in greater detail below, through the use of intelligent event masks, only those events that require application processing are ever sent back to the server. This puts all of the user interface workload at its most appropriate location, the user's machine. It allows the server components to process data in a bulk transaction oriented fashion rather than a highly interactive event driven method.
- the Windows operating system uses an event queue to process and sequence events (such as key strokes, mouse clicks, etc.).
- events such as key strokes are delivered to a window currently in focus.
- the process becomes somewhat complicated if a key stroke causes another window to become active.
- it is critical that the proper key strokes get sent to the intended window.
- FIG. 3 shows idealized keystroke processing. For example, if a user is positioned on a menu bar and presses an ‘A’, a new record is added. Also, the menu bar is disabled, and the first edit control becomes active. If the user types ‘AJohn’ rapidly, the ‘A’ disables the menu and activates the edit control. However, it is important that the ‘J’ not be removed from the event queue until the edit control has focus. If it were removed between the time the menu was disabled and the edit control was activated, it would be lost since it would be sent to the now disabled menu bar.
- keystrokes can become lost as a result of network delay.
- the ‘A’ is sent to the active menu bar.
- the server processes the event and disables the menu command.
- the ‘J’ keystroke is sent to the still active menu bar.
- the ‘J’ stroke is processed by the server.
- the menu bar has been disabled (by the ‘A’ keystroke), and the ‘J’ keystroke is therefore ignored.
- the server disables the menu bar, it activates the edit control command.
- the ‘o’ keystroke is processed and is placed first in edit control instead of ‘J’ as intended.
- an inventive event loop system is provided as shown in FIG. 5.
- the event loop scans the Windows event queue and only removes messages that are allowed based on an event mask.
- the event loop also responds to special synchronization messages to recursively call and exit the event loop to maintain stack synchronization between the View Manager and server.
- Step 50 the system looks for a message on the event queue A determination is made at Step 52 whether the event is an allowed event. If not, then at Step 54 the system determines whether there are any more events. If there are more events, the process returns to Step 50 .
- Step 52 If at Step 52 it is found that the event is an allowed event, then at Step 56 a determination is made whether it should be processed locally. If so, a message is dispatched at Step 58 and the process moves to Step 54 . If the event is not to be processed locally, it is sent to the server at Step 60 , and the process moves to Step 54 .
- Step 54 If at Step 54 , a determination is made that there are no more events, then the system waits at Step 62 for user generated events or server generated events. Thereafter at Step 64 , a determination is made whether an exit synchronization message has been received. If so, the process exits the event loop at 66 . If not, then at Step 68 , a determination is made whether the message is a layer synchronization message from the server. If so, the process recursively calls the event loop at Step 70 . If not, the process returns to Step 50 .
- the inventive system allows remote high speed data entry while maintaining keystroke synchronization.
- the system is scaleable to a large number, e.g., hundreds, of concurrent users. It provides a sophisticated user interface at the client machine controlled by the server using a low bandwidth connection (such as a 28.8 kbps modem connection) and minimal client resources.
Abstract
Description
- 1. Technical Field
- The present invention relates generally to client-server processing and, more particularly, to an application environment wherein application logic and business rules reside on a server to which users attach from client machines that have independent graphical user interface (GUI) processing.
- 2. Description of the Related Art
- The computer industry has changed dramatically over the past few years and that, coupled with the explosive growth of the Internet, has changed the way people interact with and access information. The growth of the Graphical User Interface (GUI) and the World Wide Web, the graphical side of the Internet, has changed users' expectations of how they interact with information.
- These changes present new challenges in data processing. While data processing has traditionally been performed internally, e.g., within a company site, the new global information access infrastructure allows remote data processing.
- Current remote control systems that can be adapted for remote data processing such as PCAnywhere or Citrix Servers have two significant drawbacks. First, their system overhead requirements keep them from being scaled to a large number of users. Second, keyboard interaction takes place essentially on a character by character basis. In tests of remote control systems, and character based systems such as Unix telnet, the character by character method was found unacceptable over the Internet for sustained usage of the program. With delay times typically of ¼ to ½ of a second, and sometimes more, it becomes very difficult for data entry personnel to develop any rhythm that allows for high speed entry. Using ActiveX controls and other methods based on standard Remote Procedure Call (RPC) implementations requires too much bandwidth to perform acceptably over limited speed connections such as a 28.8 kbps connection. Moreover, additional installation is needed on the client side. Web browser based implementations do not have interactive field by field validation, lookups, or help needed for large scale applications. In addition, they do not allow multiple overlapping windows.
- Some operating systems (such as the Windows operating system) use an event queue to process and sequence events (such as key strokes, mouse clicks, etc.). Generally, events such as key strokes are simply delivered to the window that is currently active. This, however, becomes somewhat complicated if a key stroke is able to activate another window. As fast users often type ahead, there is no assurance that key strokes will be sent to the intended window.
- A primary object of the present invention is to provide a network-based system that allows for high speed data entry at a remote client.
- A further object of the invention is to provide a network-based system for remote data processing in which substantially all application logic and business rules reside on a common server, and GUI processing is performed separately at a client machine.
- A further object of the invention is to provide a network-based system providing a sophisticated user interface at a client machine controlled by a server using a low bandwidth connection (such as a 28.8 kbps modem connection) and minimal client resources.
- Another object of the invention is to provide a network-based system for remote data processing that is scaleable to a large number, e.g., hundreds, of concurrent users.
- These and other objectives are accomplished by a network-based system in which application logic and business rules reside on a server to which a user attaches from a client machine. The system includes a view manager residing on the client machine for generating a graphical user interface (GUI) environment for the user. An application engine resides on the server for controlling the view manager. Events in an event queue at the client machine are parsed to determine which events require application processing. Events requiring application processing are sent to the server and other events are left in the event queue. The system also maintains stack synchronization between the client machine and the server.
- The inventive system allows remote high speed data entry while maintaining keystroke synchronization. The system is scaleable to a large number, e.g., hundreds, of concurrent users. It provides a sophisticated user interface at the client machine controlled by the server using a low bandwidth connection (such as a 28.8 kbps modem connection) and minimal client resources.
- The foregoing has outlined some of the more pertinent objects and features of the present invention. These objects should be construed to be merely illustrative of some of the more prominent features and applications of the invention. Many other beneficial results can be attained by applying the disclosed invention in a different manner or modifying the invention as will be described. Accordingly, other objects and a fuller understanding of the invention may be had by referring to the following Detailed Description of the Preferred Embodiment.
- For a more complete understanding of the present invention and the advantages thereof, reference should be made to the following Detailed Description taken in connection with the accompanying drawings in which:
- FIG. 1 shows an illustrative network environment in which the inventive system is implemented;
- FIG. 2 is a simplified block diagram of the system;
- FIG. 3 is a block diagram illustrating idealized keystroke processing;
- FIG. 4 is a block diagram illustrating the effects of network delay in keystroke processing; and
- FIG. 5 is a flow chart illustrating the event loop system in accordance with the present invention.
- A representative client-server network environment in which the present invention can be implemented is illustrated in FIG. 1. A client machine10 is connected to an
application server platform 12 vianetwork 14. Thenetwork 14 can be the Internet, an Intranet or other network connection. It preferably comprises the Internet's World Wide Web, making information accessible remotely using view manager software.Application server platform 12 is one of a plurality of servers that are accessible by the clients, one of which is illustrated by the machine 10. - The client machine10 includes a processor 11, an
operating system 13, a graphical user interface 15, and a ViewManager 16. - A representative
application server platform 12 comprises aprocessor 18 such as, e.g., an IBM RISC System/6000 computer (a reduced instruction set or so-called RISC-based workstation) running an Operating System 20 such as, e.g., the Windows NT Operating System. Theplatform 12 also includes anapplication server program 22. Theplatform 12 also preferably includes a graphical user interface (GUI) 24 for management and administration. In addition, theapplication server 22 includes an Application Programming Interface (API) 23 that provides extensions enabling application developers to extend and/or customize the core functionality. - A representative client is a personal computer (PC) workstation that is x86-, PowerPC®- or RISC-based, that includes an operating system such as Microsoft Windows 3.1 and Windows 95 (or higher), and that includes the View
Manager 16. - Briefly, in accordance with the invention, substantially all application logic and business rules reside on the common Windows NT
server 12. The client 10 preferably comprises a so-called thin client (with minimal client resources) having full Graphical User Interface (GUI) functionality, but containing substantially no application level intelligence. The thin client 10 is capable of performing well using a 28.8 modem connection through the Internet. The inventive system is scaleable to large numbers, e.g., hundreds of concurrent users. - In the inventive system, the normal Windows components are separated into two distinct objects: the data model (which contains substantially all of the information about an object such as color, size, font, position, etc.) and the View Manager (which uses information from the data model to construct an actual GUI element). The data model resides on the server, and the View Manager resides on the client machine. The system includes a message passing architecture that allows the data model and the View Manager to communicate with each other. The View Manager uses information from the data model (obtained from a message) to construct a GUI element, and then sends messages to the data model if the user changes any of the view characteristics. These messages can be sent locally or over any TCP/IP connection.
- FIG. 2 is a simplified block diagram illustrating system components in greater detail. The underlying architecture is based on an n-tier paradigm using a message passing IPC (InterProcess Communications) protocol. Each tier in the system is composed of one or more processes referred to as Managers. On the client side, the
View Manager 16 is responsible for rendering graphical elements, interfacing with the user, and forwarding events to theserver 12. On the server side, the Forms Manager 32 (using the data model) provides the control structures that manage the View Manager objects, respond to events, and interface with the application layer to provide program flow control. While theForms Manager 32 controls the GUI elements on theView Manager 16, it preferably has no actual GUI elements itself. - At its lowest level, the system is composed of three basic components: a remote object client10, a
remote object server 12, and adispatcher 14. The objects communicate with each other by sending messages. A message is a packet of bytes passed from one object to another. There is no predefined structure to a message except that defined by the sending and receiving objects. The dispatcher preferably uses a simple message passing structure based on the Winsock/Berkeley sockets TCP/IP interface to communicate between objects. Parameters are placed directly into a message buffer. The message is sent via the dispatcher to the remote system using standard TCP/IP socket calls. It is then passed to the target object. The arguments are removed from the message and the appropriate code is called to perform the function. A flag indicates if a response is required to the message. Not only does this approach simplify the steps needed to build the application, but it gives us complete control over the underlying communications parameters and requires no specialized software to be installed on the client or the server. - The client and server components at this lowest level are responsible for routing a message received from the dispatcher to the appropriate object. The
View Manager 16 implements only the client component preferably using Windows Asynchronous Sockets to allow it to run in the Windows 3.1 and Windows 95 environments. The server software implements both the server and the client components in a multi-threaded environment preferably using a standard Berkeley sockets style interface. By implementing both server and client components, the server process can function as both a server for theView Manager 16, and as a client to other processes. This provides the foundation for the n-tier architecture. - The Forms Management layer allows GUI elements to be created and controlled by the
server 12 on a remote client 10. Using the messaging system to create and manage remote objects, the server can control sophisticated user interfaces using a low bandwidth connection and minimal client resources. - Layered on top of the
Forms Manager 32 is aDatabase Manager 34 designed to provide relational database access to information, andApplication Specific Code 36 that provides the business rules and program control logic. Both of these layers execute in the multi-threaded server process and have full access to the communications layer. This provides the core functionality of the system. TheView Manager 16 is a relatively small, simple Windows application that requires virtually no specialized client software aside from a standard TCP/IP interface. The server components provide all application control logic and business rules. Together they form a very powerful framework to provide sophisticated GUI applications that can run over low bandwidth communication links. - Thus, the View Manager30, which resides on the client workstation 10, provides a full GUI environment and communicates with the
Forms Manager 32 through a message architecture. It is responsible for all user input processing and output rendering. As will be described in greater detail below, through the use of intelligent event masks, only those events that require application processing are ever sent back to the server. This puts all of the user interface workload at its most appropriate location, the user's machine. It allows the server components to process data in a bulk transaction oriented fashion rather than a highly interactive event driven method. - As previously discussed, the Windows operating system uses an event queue to process and sequence events (such as key strokes, mouse clicks, etc.). Usually events, such as key strokes are delivered to a window currently in focus. However, the process becomes somewhat complicated if a key stroke causes another window to become active. As fast users often type ahead, it is critical that the proper key strokes get sent to the intended window.
- FIG. 3 shows idealized keystroke processing. For example, if a user is positioned on a menu bar and presses an ‘A’, a new record is added. Also, the menu bar is disabled, and the first edit control becomes active. If the user types ‘AJohn’ rapidly, the ‘A’ disables the menu and activates the edit control. However, it is important that the ‘J’ not be removed from the event queue until the edit control has focus. If it were removed between the time the menu was disabled and the edit control was activated, it would be lost since it would be sent to the now disabled menu bar.
- As shown in FIG. 4, keystrokes can become lost as a result of network delay. When the user (positioned on a menu bar) types ‘AJohn’ rapidly, the ‘A’ is sent to the active menu bar. There is however network delay before the server processes the event and disables the menu command. Because of the delay, the ‘J’ keystroke is sent to the still active menu bar. There is also a delay before the ‘J’ stroke is processed by the server. By the time the ‘J’ stroke is processed, the menu bar has been disabled (by the ‘A’ keystroke), and the ‘J’ keystroke is therefore ignored.
- After the server disables the menu bar, it activates the edit control command. By this time, the ‘o’ keystroke is processed and is placed first in edit control instead of ‘J’ as intended.
- To avoid this problem, an inventive event loop system is provided as shown in FIG. 5. In brief, the event loop scans the Windows event queue and only removes messages that are allowed based on an event mask. The event loop also responds to special synchronization messages to recursively call and exit the event loop to maintain stack synchronization between the View Manager and server.
- At
Step 50 the system looks for a message on the event queue A determination is made at Step 52 whether the event is an allowed event. If not, then atStep 54 the system determines whether there are any more events. If there are more events, the process returns to Step 50. - If at Step52 it is found that the event is an allowed event, then at Step 56 a determination is made whether it should be processed locally. If so, a message is dispatched at
Step 58 and the process moves to Step 54. If the event is not to be processed locally, it is sent to the server at Step 60, and the process moves to Step 54. - If at
Step 54, a determination is made that there are no more events, then the system waits atStep 62 for user generated events or server generated events. Thereafter atStep 64, a determination is made whether an exit synchronization message has been received. If so, the process exits the event loop at 66. If not, then atStep 68, a determination is made whether the message is a layer synchronization message from the server. If so, the process recursively calls the event loop at Step 70. If not, the process returns to Step 50. - The inventive system allows remote high speed data entry while maintaining keystroke synchronization. The system is scaleable to a large number, e.g., hundreds, of concurrent users. It provides a sophisticated user interface at the client machine controlled by the server using a low bandwidth connection (such as a 28.8 kbps modem connection) and minimal client resources.
Claims (4)
Priority Applications (6)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/164,244 US6377973B2 (en) | 1998-09-30 | 1998-09-30 | Event management in a system with application and graphical user interface processing adapted to display predefined graphical elements resides separately on server and client machine |
PCT/US1999/022549 WO2000019328A1 (en) | 1998-09-30 | 1999-09-30 | Event management in a system with separate application and graphical user interface processing |
CA002346028A CA2346028C (en) | 1998-09-30 | 1999-09-30 | Event management in a system with separate application and graphical user interface processing |
EP99952977A EP1133735A4 (en) | 1998-09-30 | 1999-09-30 | Event management in a system with separate application and graphical user interface processing |
AU65022/99A AU6502299A (en) | 1998-09-30 | 1999-09-30 | Event management in a system with separate application and graphical user interface processing |
US10/055,552 US6944644B2 (en) | 1998-09-30 | 2002-01-23 | Event management in a system with separate application and graphical user interface processing |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/164,244 US6377973B2 (en) | 1998-09-30 | 1998-09-30 | Event management in a system with application and graphical user interface processing adapted to display predefined graphical elements resides separately on server and client machine |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/055,552 Continuation US6944644B2 (en) | 1998-09-30 | 2002-01-23 | Event management in a system with separate application and graphical user interface processing |
Publications (2)
Publication Number | Publication Date |
---|---|
US20020013804A1 true US20020013804A1 (en) | 2002-01-31 |
US6377973B2 US6377973B2 (en) | 2002-04-23 |
Family
ID=22593611
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/164,244 Expired - Fee Related US6377973B2 (en) | 1998-09-30 | 1998-09-30 | Event management in a system with application and graphical user interface processing adapted to display predefined graphical elements resides separately on server and client machine |
US10/055,552 Expired - Fee Related US6944644B2 (en) | 1998-09-30 | 2002-01-23 | Event management in a system with separate application and graphical user interface processing |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/055,552 Expired - Fee Related US6944644B2 (en) | 1998-09-30 | 2002-01-23 | Event management in a system with separate application and graphical user interface processing |
Country Status (5)
Country | Link |
---|---|
US (2) | US6377973B2 (en) |
EP (1) | EP1133735A4 (en) |
AU (1) | AU6502299A (en) |
CA (1) | CA2346028C (en) |
WO (1) | WO2000019328A1 (en) |
Cited By (15)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20070233902A1 (en) * | 2006-03-30 | 2007-10-04 | Alan Trefler | User interface methods and apparatus for rules processing |
US20080208785A1 (en) * | 2006-03-30 | 2008-08-28 | Pegasystems, Inc. | User interface methods and apparatus for rules processing |
US20100107137A1 (en) * | 2004-05-26 | 2010-04-29 | Pegasystems Inc. | Methods and apparatus for integration of declarative rule-based processing with procedural programming in a digital data-processing evironment |
US8250525B2 (en) | 2007-03-02 | 2012-08-21 | Pegasystems Inc. | Proactive performance management for multi-user enterprise software systems |
US8335704B2 (en) | 2005-01-28 | 2012-12-18 | Pegasystems Inc. | Methods and apparatus for work management and routing |
US8880487B1 (en) | 2011-02-18 | 2014-11-04 | Pegasystems Inc. | Systems and methods for distributed rules processing |
US8924335B1 (en) | 2006-03-30 | 2014-12-30 | Pegasystems Inc. | Rule-based user interface conformance methods |
US9195936B1 (en) | 2011-12-30 | 2015-11-24 | Pegasystems Inc. | System and method for updating or modifying an application without manual coding |
US9678719B1 (en) | 2009-03-30 | 2017-06-13 | Pegasystems Inc. | System and software for creation and modification of software |
US10467200B1 (en) | 2009-03-12 | 2019-11-05 | Pegasystems, Inc. | Techniques for dynamic data processing |
US10469396B2 (en) | 2014-10-10 | 2019-11-05 | Pegasystems, Inc. | Event processing with enhanced throughput |
US10698647B2 (en) | 2016-07-11 | 2020-06-30 | Pegasystems Inc. | Selective sharing for collaborative application usage |
US10698599B2 (en) | 2016-06-03 | 2020-06-30 | Pegasystems, Inc. | Connecting graphical shapes using gestures |
US11048488B2 (en) | 2018-08-14 | 2021-06-29 | Pegasystems, Inc. | Software code optimizer and method |
US11567945B1 (en) | 2020-08-27 | 2023-01-31 | Pegasystems Inc. | Customized digital content generation systems and methods |
Families Citing this family (57)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6377973B2 (en) * | 1998-09-30 | 2002-04-23 | Emrys Technologies, Ltd. | Event management in a system with application and graphical user interface processing adapted to display predefined graphical elements resides separately on server and client machine |
US7673323B1 (en) | 1998-10-28 | 2010-03-02 | Bea Systems, Inc. | System and method for maintaining security in a distributed computer network |
US6158010A (en) | 1998-10-28 | 2000-12-05 | Crosslogix, Inc. | System and method for maintaining security in a distributed computer network |
US6775658B1 (en) * | 1999-12-21 | 2004-08-10 | Mci, Inc. | Notification by business rule trigger control |
US7051069B2 (en) | 2000-09-28 | 2006-05-23 | Bea Systems, Inc. | System for managing logical process flow in an online environment |
US7103652B1 (en) * | 2000-12-23 | 2006-09-05 | Emc Corporation | Ambiguity-purging and template-conflict-resolution in computer network events-notification |
US7499948B2 (en) * | 2001-04-16 | 2009-03-03 | Bea Systems, Inc. | System and method for web-based personalization and ecommerce management |
GB2375851A (en) * | 2001-05-24 | 2002-11-27 | 3G Lab Ltd | Data processing device with generated graphic user interface |
US7392546B2 (en) * | 2001-06-11 | 2008-06-24 | Bea Systems, Inc. | System and method for server security and entitlement processing |
WO2003036609A1 (en) * | 2001-10-24 | 2003-05-01 | Bea Systems, Inc. | Portal administration tool |
US7350226B2 (en) * | 2001-12-13 | 2008-03-25 | Bea Systems, Inc. | System and method for analyzing security policies in a distributed computer network |
US7725560B2 (en) | 2002-05-01 | 2010-05-25 | Bea Systems Inc. | Web service-enabled portlet wizard |
US7496687B2 (en) | 2002-05-01 | 2009-02-24 | Bea Systems, Inc. | Enterprise application platform |
US7653930B2 (en) | 2003-02-14 | 2010-01-26 | Bea Systems, Inc. | Method for role and resource policy management optimization |
US6917975B2 (en) * | 2003-02-14 | 2005-07-12 | Bea Systems, Inc. | Method for role and resource policy management |
US8831966B2 (en) | 2003-02-14 | 2014-09-09 | Oracle International Corporation | Method for delegated administration |
US7591000B2 (en) * | 2003-02-14 | 2009-09-15 | Oracle International Corporation | System and method for hierarchical role-based entitlements |
US7415478B2 (en) | 2003-02-20 | 2008-08-19 | Bea Systems, Inc. | Virtual repository complex content model |
US7483904B2 (en) * | 2003-02-20 | 2009-01-27 | Bea Systems, Inc. | Virtual repository content model |
US20040167871A1 (en) * | 2003-02-20 | 2004-08-26 | Bea Systems, Inc. | Content mining for virtual content repositories |
US7840614B2 (en) * | 2003-02-20 | 2010-11-23 | Bea Systems, Inc. | Virtual content repository application program interface |
US7293286B2 (en) * | 2003-02-20 | 2007-11-06 | Bea Systems, Inc. | Federated management of content repositories |
US20040167880A1 (en) * | 2003-02-20 | 2004-08-26 | Bea Systems, Inc. | System and method for searching a virtual repository content |
US20040167868A1 (en) * | 2003-02-20 | 2004-08-26 | Bea Systems, Inc. | System and method for a virtual content repository |
US7562298B2 (en) | 2003-02-20 | 2009-07-14 | Bea Systems, Inc. | Virtual content repository browser |
US7213235B2 (en) * | 2003-02-21 | 2007-05-01 | Sap Ag | Method for using a business model user interface |
US7810036B2 (en) * | 2003-02-28 | 2010-10-05 | Bea Systems, Inc. | Systems and methods for personalizing a portal |
US7805523B2 (en) * | 2004-03-15 | 2010-09-28 | Mitchell David C | Method and apparatus for partial updating of client interfaces |
EP1738271A4 (en) * | 2004-03-15 | 2008-12-03 | Bungee Labs Inc | Declarative computer programming language method and system |
US7774601B2 (en) * | 2004-04-06 | 2010-08-10 | Bea Systems, Inc. | Method for delegated administration |
US7246138B2 (en) * | 2004-04-13 | 2007-07-17 | Bea Systems, Inc. | System and method for content lifecycles in a virtual content repository that integrates a plurality of content repositories |
US20060028252A1 (en) * | 2004-04-13 | 2006-02-09 | Bea Systems, Inc. | System and method for content type management |
US7580953B2 (en) * | 2004-04-13 | 2009-08-25 | Bea Systems, Inc. | System and method for schema lifecycles in a virtual content repository that integrates a plurality of content repositories |
US7240076B2 (en) * | 2004-04-13 | 2007-07-03 | Bea Systems, Inc. | System and method for providing a lifecycle for information in a virtual content repository |
US20060041558A1 (en) * | 2004-04-13 | 2006-02-23 | Mccauley Rodney | System and method for content versioning |
US20050228784A1 (en) * | 2004-04-13 | 2005-10-13 | Bea Systems, Inc. | System and method for batch operations in a virtual content repository |
US7475091B2 (en) * | 2004-04-13 | 2009-01-06 | Bea Systems, Inc. | System and method for viewing a virtual content repository |
US20050251512A1 (en) * | 2004-04-13 | 2005-11-10 | Bea Systems, Inc. | System and method for searching a virtual content repository |
US7543032B2 (en) * | 2004-10-22 | 2009-06-02 | Canyonbridge, Inc. | Method and apparatus for associating messages with data elements |
US8627344B2 (en) * | 2004-12-15 | 2014-01-07 | Siebel Systems, Inc. | Methods and apparatuses for user interface management |
US7752205B2 (en) * | 2005-09-26 | 2010-07-06 | Bea Systems, Inc. | Method and system for interacting with a virtual content repository |
US7483893B2 (en) * | 2005-09-26 | 2009-01-27 | Bae Systems, Inc. | System and method for lightweight loading for managing content |
US20070073784A1 (en) * | 2005-09-26 | 2007-03-29 | Bea Systems, Inc. | System and method for type inheritance for content management |
US20070073673A1 (en) * | 2005-09-26 | 2007-03-29 | Bea Systems, Inc. | System and method for content management security |
US7953734B2 (en) | 2005-09-26 | 2011-05-31 | Oracle International Corporation | System and method for providing SPI extensions for content management system |
US7917537B2 (en) * | 2005-09-26 | 2011-03-29 | Oracle International Corporation | System and method for providing link property types for content management |
US20070073674A1 (en) * | 2005-09-26 | 2007-03-29 | Bea Systems, Inc. | System and method for providing federated events for content management systems |
US7818344B2 (en) * | 2005-09-26 | 2010-10-19 | Bea Systems, Inc. | System and method for providing nested types for content management |
US20070174454A1 (en) * | 2006-01-23 | 2007-07-26 | Mitchell David C | Method and apparatus for accessing Web services and URL resources for both primary and shared users over a reverse tunnel mechanism |
US7581190B2 (en) * | 2006-07-19 | 2009-08-25 | Microsoft Corporation | Constructing user interfaces on top of cmdlets |
US8463852B2 (en) | 2006-10-06 | 2013-06-11 | Oracle International Corporation | Groupware portlets for integrating a portal with groupware systems |
US8220002B2 (en) * | 2008-01-25 | 2012-07-10 | Microsoft Corporation | Isolation of user-interactive components |
US8468070B1 (en) * | 2009-04-16 | 2013-06-18 | Amazon Technologies, Inc. | Local rendering in lieu of streaming |
US8650247B2 (en) * | 2010-04-05 | 2014-02-11 | Microsoft Corporation | Four tier architecture for implementing thin clients |
CN106055314A (en) * | 2016-05-19 | 2016-10-26 | 努比亚技术有限公司 | Terminal and method for application sharing interface updating management applied to terminal |
US11003463B2 (en) | 2016-09-16 | 2021-05-11 | Rocket Software, Inc. | Virtual desktop |
FR3109923A1 (en) | 2020-05-06 | 2021-11-12 | Sp-Trailer | Self-propelled vehicle for handling, in particular semi-trailers |
Family Cites Families (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5341477A (en) * | 1989-02-24 | 1994-08-23 | Digital Equipment Corporation | Broker for computer network server selection |
US5900870A (en) * | 1989-06-30 | 1999-05-04 | Massachusetts Institute Of Technology | Object-oriented computer user interface |
US5557798A (en) * | 1989-07-27 | 1996-09-17 | Tibco, Inc. | Apparatus and method for providing decoupling of data exchange details for providing high performance communication between software processes |
US5187787B1 (en) * | 1989-07-27 | 1996-05-07 | Teknekron Software Systems Inc | Apparatus and method for providing decoupling of data exchange details for providing high performance communication between software processes |
US5613106A (en) * | 1989-09-15 | 1997-03-18 | Motorola, Inc. | Method for processing and storing a transaction in a distributed database system |
US5410704A (en) * | 1989-11-30 | 1995-04-25 | Motorola, Inc. | Table modifiable edit functions with order-effective edit rules |
US5278984A (en) * | 1990-12-19 | 1994-01-11 | Bull Hn Information Systems Inc. | Method for managing requests by specifying time intervals for transmitting a minimum number of messages for specific destinations and priority levels |
US5640577A (en) * | 1991-12-30 | 1997-06-17 | Davox Corporation | Data processing system with automated at least partial forms completion |
US5649190A (en) * | 1994-06-14 | 1997-07-15 | Harris Corporation | Multi-model database system for dynamic creation and maintenance of complex objects in a real time environment |
JP3487644B2 (en) * | 1994-07-19 | 2004-01-19 | シャープ株式会社 | Graphical user interface creation device |
US5602998A (en) * | 1994-12-22 | 1997-02-11 | Unisys Corporation | Dequeue instruction in a system architecture for improved message passing and process synchronization |
US5644720A (en) * | 1995-07-31 | 1997-07-01 | West Publishing Company | Interprocess communications interface for managing transaction requests |
US6125383A (en) * | 1997-06-11 | 2000-09-26 | Netgenics Corp. | Research system using multi-platform object oriented program language for providing objects at runtime for creating and manipulating biological or chemical data |
US6377973B2 (en) * | 1998-09-30 | 2002-04-23 | Emrys Technologies, Ltd. | Event management in a system with application and graphical user interface processing adapted to display predefined graphical elements resides separately on server and client machine |
-
1998
- 1998-09-30 US US09/164,244 patent/US6377973B2/en not_active Expired - Fee Related
-
1999
- 1999-09-30 WO PCT/US1999/022549 patent/WO2000019328A1/en active Application Filing
- 1999-09-30 EP EP99952977A patent/EP1133735A4/en not_active Withdrawn
- 1999-09-30 CA CA002346028A patent/CA2346028C/en not_active Expired - Fee Related
- 1999-09-30 AU AU65022/99A patent/AU6502299A/en not_active Abandoned
-
2002
- 2002-01-23 US US10/055,552 patent/US6944644B2/en not_active Expired - Fee Related
Cited By (23)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20100107137A1 (en) * | 2004-05-26 | 2010-04-29 | Pegasystems Inc. | Methods and apparatus for integration of declarative rule-based processing with procedural programming in a digital data-processing evironment |
US8479157B2 (en) | 2004-05-26 | 2013-07-02 | Pegasystems Inc. | Methods and apparatus for integration of declarative rule-based processing with procedural programming in a digital data-processing evironment |
US8959480B2 (en) | 2004-05-26 | 2015-02-17 | Pegasystems Inc. | Methods and apparatus for integration of declarative rule-based processing with procedural programming in a digital data-processing environment |
US8335704B2 (en) | 2005-01-28 | 2012-12-18 | Pegasystems Inc. | Methods and apparatus for work management and routing |
US10838569B2 (en) | 2006-03-30 | 2020-11-17 | Pegasystems Inc. | Method and apparatus for user interface non-conformance detection and correction |
US20080208785A1 (en) * | 2006-03-30 | 2008-08-28 | Pegasystems, Inc. | User interface methods and apparatus for rules processing |
US9658735B2 (en) | 2006-03-30 | 2017-05-23 | Pegasystems Inc. | Methods and apparatus for user interface optimization |
US20070233902A1 (en) * | 2006-03-30 | 2007-10-04 | Alan Trefler | User interface methods and apparatus for rules processing |
US8924335B1 (en) | 2006-03-30 | 2014-12-30 | Pegasystems Inc. | Rule-based user interface conformance methods |
US9189361B2 (en) | 2007-03-02 | 2015-11-17 | Pegasystems Inc. | Proactive performance management for multi-user enterprise software systems |
US8250525B2 (en) | 2007-03-02 | 2012-08-21 | Pegasystems Inc. | Proactive performance management for multi-user enterprise software systems |
US10467200B1 (en) | 2009-03-12 | 2019-11-05 | Pegasystems, Inc. | Techniques for dynamic data processing |
US9678719B1 (en) | 2009-03-30 | 2017-06-13 | Pegasystems Inc. | System and software for creation and modification of software |
US8880487B1 (en) | 2011-02-18 | 2014-11-04 | Pegasystems Inc. | Systems and methods for distributed rules processing |
US9270743B2 (en) | 2011-02-18 | 2016-02-23 | Pegasystems Inc. | Systems and methods for distributed rules processing |
US9195936B1 (en) | 2011-12-30 | 2015-11-24 | Pegasystems Inc. | System and method for updating or modifying an application without manual coding |
US10572236B2 (en) | 2011-12-30 | 2020-02-25 | Pegasystems, Inc. | System and method for updating or modifying an application without manual coding |
US10469396B2 (en) | 2014-10-10 | 2019-11-05 | Pegasystems, Inc. | Event processing with enhanced throughput |
US11057313B2 (en) | 2014-10-10 | 2021-07-06 | Pegasystems Inc. | Event processing with enhanced throughput |
US10698599B2 (en) | 2016-06-03 | 2020-06-30 | Pegasystems, Inc. | Connecting graphical shapes using gestures |
US10698647B2 (en) | 2016-07-11 | 2020-06-30 | Pegasystems Inc. | Selective sharing for collaborative application usage |
US11048488B2 (en) | 2018-08-14 | 2021-06-29 | Pegasystems, Inc. | Software code optimizer and method |
US11567945B1 (en) | 2020-08-27 | 2023-01-31 | Pegasystems Inc. | Customized digital content generation systems and methods |
Also Published As
Publication number | Publication date |
---|---|
EP1133735A4 (en) | 2007-11-14 |
AU6502299A (en) | 2000-04-17 |
CA2346028A1 (en) | 2000-04-06 |
US20020069246A1 (en) | 2002-06-06 |
US6944644B2 (en) | 2005-09-13 |
WO2000019328A1 (en) | 2000-04-06 |
EP1133735A1 (en) | 2001-09-19 |
CA2346028C (en) | 2007-12-04 |
US6377973B2 (en) | 2002-04-23 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US6377973B2 (en) | Event management in a system with application and graphical user interface processing adapted to display predefined graphical elements resides separately on server and client machine | |
US6323881B1 (en) | Web based GUI server and method for a telecommunications node | |
US7028307B2 (en) | Data management framework for policy management | |
US8285807B2 (en) | Method and system for remote industrial factory automation control of a local system | |
US6041365A (en) | Apparatus and method for high performance remote application gateway servers | |
US6950991B2 (en) | Interacting with software applications displayed in a web page | |
US7555529B2 (en) | Interacting with software applications displayed in a web page | |
US5293619A (en) | Method and apparatus for collaborative use of application program | |
EP1727045A2 (en) | Application framework for use with net-centric application program architectures | |
US6038593A (en) | Remote application control for low bandwidth application sharing | |
US6401109B1 (en) | Virtual socket for JAVA interprocess communication | |
MXPA03006025A (en) | Exchanging electronic messages between a host computer system and a distributed computer system. | |
WO2001075836A2 (en) | Remote control system | |
CA2119215A1 (en) | Method and apparatus for linking object managers for cooperative processing in an object oriented computing environment | |
JPH07160608A (en) | System and method for display of program application | |
US7974990B2 (en) | Managing program applications | |
US6697088B1 (en) | Graphical presentation system | |
US20040049530A1 (en) | Distributed computer system using a graphical user interface toolkit | |
KR100330535B1 (en) | Improved presentation scheme for communication between user stations and application programs | |
US7437376B2 (en) | Scalable object model | |
US20070204054A1 (en) | ASN.1 protocol processor and method for ASN.1 protocol processing | |
US7197712B2 (en) | Server visualization and control | |
JP2002007651A (en) | Workflow preparation system | |
Muller et al. | Multi-thread interface for telecommunications applications | |
US20080271051A1 (en) | Component-Oriented Application Servers |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: EMRYS SOLUTIONS, INC., TEXAS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:GIDEON, CARL A.;REEL/FRAME:009657/0839 Effective date: 19981125 |
|
AS | Assignment |
Owner name: EMRYS PARTNERS, LTD., TEXAS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:EMRYS SOLUTIONS, INC.;REEL/FRAME:010083/0407 Effective date: 19990519 |
|
FEPP | Fee payment procedure |
Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: SMALL ENTITY |
|
AS | Assignment |
Owner name: EMRYS TECHNOLOGIES, LTD., TEXAS Free format text: CHANGE OF NAME;ASSIGNOR:EMRYS PARTNERS, LTD.;REEL/FRAME:015177/0435 Effective date: 20011011 |
|
FEPP | Fee payment procedure |
Free format text: PAYER NUMBER DE-ASSIGNED (ORIGINAL EVENT CODE: RMPN); ENTITY STATUS OF PATENT OWNER: SMALL ENTITY Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: SMALL ENTITY |
|
FPAY | Fee payment |
Year of fee payment: 4 |
|
FPAY | Fee payment |
Year of fee payment: 8 |
|
REMI | Maintenance fee reminder mailed | ||
LAPS | Lapse for failure to pay maintenance fees | ||
STCH | Information on status: patent discontinuation |
Free format text: PATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362 |
|
FP | Lapsed due to failure to pay maintenance fee |
Effective date: 20140423 |