US20080281911A1 - Synchronizing a client user interface with a server backend - Google Patents

Synchronizing a client user interface with a server backend Download PDF

Info

Publication number
US20080281911A1
US20080281911A1 US12/178,598 US17859808A US2008281911A1 US 20080281911 A1 US20080281911 A1 US 20080281911A1 US 17859808 A US17859808 A US 17859808A US 2008281911 A1 US2008281911 A1 US 2008281911A1
Authority
US
United States
Prior art keywords
ui
presentation
server system
client system
document
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.)
Abandoned
Application number
US12/178,598
Inventor
John W. COMEAU
Gin Yee Ng
Victor Ka Chun Yu
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
International Business Machines Corp
Original Assignee
International Business Machines Corp
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Priority to CA2438362 priority Critical
Priority to CA 2438362 priority patent/CA2438362C/en
Priority to US10/917,181 priority patent/US7519739B2/en
Application filed by International Business Machines Corp filed Critical International Business Machines Corp
Priority to US12/178,598 priority patent/US20080281911A1/en
Publication of US20080281911A1 publication Critical patent/US20080281911A1/en
Application status is Abandoned legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network-specific arrangements or communication protocols supporting networked applications
    • H04L67/08Network-specific arrangements or communication protocols supporting networked applications adapted for terminal emulation, e.g. telnet
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network-specific arrangements or communication protocols supporting networked applications
    • H04L67/10Network-specific arrangements or communication protocols supporting networked applications in which an application is distributed across nodes in the network
    • H04L67/1095Network-specific arrangements or communication protocols supporting networked applications in which an application is distributed across nodes in the network for supporting replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes or user terminals or syncML
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network-specific arrangements or communication protocols supporting networked applications
    • H04L67/36Network-specific arrangements or communication protocols supporting networked applications involving the display of network or application conditions affecting the network application to the application user

Abstract

A system coupled to at least one client system, a system for synchronizing a user interface (UI) presentation to be displayed to a user of the client system to a UI description maintained by the server system, the server system comprising a UI object converter adapted for converting the UI description into one or more UI object definitions; storing each UI object definition in a document; and, transmitting the document to the client system; the client system adapted to convert the UI object definitions to UI objects to generate the UI presentation.

Description

    CLAIM OF PRIORITY
  • Under 35 USC §120, this application is a Continuation application and claims the benefit of priority to U.S. patent application Ser. No. 10/917,181, filed on Aug. 11, 2004 which claims the benefit of priority under 35 USC §119 to Canadian Application No. 2,438,362, filed Aug. 26, 2003, all of which is incorporated herein by reference.
  • FIELD OF THE INVENTION
  • This invention relates generally to client/server systems, and more particularly to the synchronization of client user interfaces with backend servers.
  • BACKGROUND
  • In a typical client/server system, client system users access an application or service on a server system through a network. Electronic commerce (“e-commerce”) applications are often based on client/server systems and may include server administration tools. For example, an electronic store maintained on the server of an e-commerce system may be accessed via a TCP/IP network by client system users.
  • Several methods exist enabling users to interact with applications stored on a server system using a client system. One approach is to download the entire application from the server system and then execute it directly on the client system. Unfortunately, there are several shortcomings with this approach. For example, any changes to data shared by multiple client systems would require synchronization.
  • A variation on this download approach is to provide virtual machine software on the client system. This helps assure that the client system will be able to run the downloaded application, however, a shortcoming exists in that it is difficult to assure that virtual machine software updates are consistent across a large number of client platforms.
  • Another approach to running applications on a client system allows programs and data to remain on the server system and for programs to execute on the server with control of these programs offered as a service to client systems. This approach has its own shortcomings. For example, the software (i.e. client application) necessary to access a service may not be available on the client system, or that software may be out-of-date.
  • With respect to the sending of user interface (“UI”) or graphical user interface (“GUI”) information to the client application from the server application for display to a user, in such a server software based approach, there are several possible schemes. In a simple scheme, the server application would send to the client application the entire graphical image for the UI. Every change to this image made by the server application would require the transmission of an updated image to the client application. This scheme is obviously inefficient and is unsuited for low-bandwidth networks such as cellular telephone networks.
  • This simple system may be improved by having the server communicate only information pertaining to those portions of the graphical image that have been changed. This improvement is well-known. A more significant improvement is achieved by replicating within the client application the same rendering logic that is used by the server application. However, there are shortcomings with these approaches. For example, the client application is completely dependent on the server application for all updates. This results in increased network usage. Most importantly, this scheme also requires that changes in server application software be synchronized with changes in client application software.
  • Thus, in a client/server environment, it is often necessary that a client application or UI be synchronized with a server application. For example, when the server application is updated to a new version or service level, the client application or UI will also require updating. The client application or UI may also need to include code to detect a new version or service level of the server application and conditionally display a different UI on the client's display screen.
  • A need therefore exists for a method of efficiently synchronizing a client application or UI with a backend server application. Accordingly, a solution that addresses, at least in part, the above and other problems is desired.
  • SUMMARY
  • According to one aspect of the invention there is provided, in a server system coupled to at least one client system, a method for synchronizing a user interface (UI) presentation to be displayed to a user of the client system to a UI description maintained by the server system, the method comprising the steps of: converting the UI description into one or more UI object definitions; storing each UI object definition in a document; and, transmitting the document to the client system; the client system adapted to convert the UI object definitions to UI objects to generate the UI presentation.
  • Preferably, the step of transmitting is responsive to a request for the UI presentation by one or more of the client system and the server system.
  • Preferably, the UI object definitions contain data for the UI presentation.
  • Preferably, the data contains computer executable code.
  • Preferably, the data is dynamic data for displaying in the UI presentation.
  • Preferably, the document is a markup language document such as an Extensible Markup Language (XML) document.
  • Preferably, the UI presentation is a graphical user interface (GUI) presentation.
  • In accordance with further aspects of the present invention there is provided an apparatus such as a server system and a client system, a method for adapting these systems, as well as articles of manufacture such as a computer readable medium having program instructions recorded thereon for practising the method of the invention.
  • Advantageously, the present invention allows for improvements in the efficiency and flexibility of synchronizing the update of UI presentations in client/sever systems. For example, as the maintenance level or version of product code on the server changes, with the present invention it is only necessary to update the server side code that builds a document describing the UI presentation.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • Further features and advantages of the embodiments of the present invention will become apparent from the following detailed description, taken in combination with the appended drawings, in which:
  • FIG. 1 is a block diagram illustrating an exemplary client/server system in accordance with an embodiment of the invention; and,
  • FIG. 2 is a flow chart illustrating operations of modules within the client/server system for synchronizing a client user interface with a server backend in accordance with an embodiment of the invention.
  • It will be noted that throughout the appended drawings, like features are identified by like reference numerals.
  • DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
  • The following detailed description of the embodiments of the present invention does not limit the implementation of the invention to any particular computer programming language. The present invention may be implemented in any computer programming language provided that the operating system (“OS”) provides the facilities that may support the requirements of the present invention. A preferred embodiment is implemented in the JAVA™ computer programming language (or other computer programming languages such as the C or C++ computer programming languages in conjunction with JAVA™). (JAVA and all JAVA-based trademarks are the trademarks of Sun Microsystems Corporation.) Any limitations presented would be a result of a particular type of operating system or computer programming language and would not be a limitation of the present invention.
  • FIG. 1 is a block diagram illustrating an exemplary client/server system 100 in accordance with an embodiment of the invention. The client/server system 100 includes a server 110 communicating with one or more clients 210 over a network 120, such as the Internet. The server 110 which may be maintained by a software product supplier or other service provider may include a database system 130 for storing and accessing user interface (“UI”) information (e.g. UI description 160, UI dynamic data 170, etc.) for one or more clients 210 and provides transaction and content searching functionality. The server 110 and client 210 are adapted to provide UI information 160, 170 in accordance with the present invention. The client 210 may be a personal computer adapted for accessing the user interface information presented by the server 110 over the network 120. The UI interface information includes information pertaining to the format 160 and content 170 of the user interfaces to be presented to client users.
  • The server's database system 130 may include a database management system (“DBMS”) coupled to a database and stored in the memory 140 of the server 110. It will be appreciated that the database system 130 may be shipped or installed without the database to or by end users. In general, the DBMS is adapted to read a query generated by the server 110 in response to a client request for UI information 160, 170 submitted over the network 120. The DBMS then executes the query against the database and provides a query result to the server 110 for presentation to the client user. It will be appreciated that the database system 130 may be stored in the memory 140 of the server 110 or stored in a distributed data processing system (not shown).
  • An example of a suitable DBMS is the DB2™ Universal Database Management System product sold by IBM™. The DBMS is a software layer interposed between the actual database (i.e. the data as stored for use by the CPU 150 of the server 110) and the users of the system. The DBMS is responsible for handling database transactions thus shielding users from the details of any specific computer hardware or database implementation. Using relational techniques, the DBMS stores, manipulates and retrieves data in the form of table-like relations typically defined by a set of columns or attributes of data types and a set of rows (i.e. records or tuples) of data. The standard database query language for dealing with relational databases implemented by most commercial DBMSs is the Structured Query Language (“SQL”).
  • The server 110 includes a central processing unit (“CPU”) 150 operatively coupled to memory 140, which also stores an operating system (not shown) for general management of the server system 110. An example of a suitable server system 110 is an IBM™ iSeries™ computer. The server 110 includes computer executable programmed instructions for directing the server 110 to implement the embodiments of the present invention. The programmed instructions may be embodied in one or more software modules resident on the server 110, for example, the UI object converter module 180 which will be described below. Alternatively, the programmed instructions may be embodied on a computer readable medium (such as a CD disk or floppy disk), which may be used for transporting the programmed instructions to the memory 140 of the server 110. Alternatively, the programmed instructions may be embedded in a computer-readable, signal-bearing medium that is uploaded to a network 120 by a vendor or supplier of the programmed instructions, and this signal-bearing medium may be downloaded to the server 110 from the network 120 by end users or potential buyers.
  • The CPU 150 of the server 110 is typically coupled to one or more devices (not shown) for receiving user queries or requests and for presenting the results of the queries or requests to users over the network 120. User queries may be transformed into a combination of SQL commands for producing one or more tables of output data, which may be incorporated in one or more UIs or Web pages for presentation to the user. The CPU 150 is coupled to memory 140 for containing programs and data such as base tables or virtual tables such as views or derived tables. The memory 140 may include a variety of storage devices including internal memory and external mass storage typically arranged in a hierarchy of storage as understood to those skilled in the art.
  • As will also be understood by those skilled in the art, the server 110 may include a number of separate servers depending on system 100 requirements. For example, the server 110 may include separate presentation, application, transaction, data, security, and edge servers.
  • Each client 210 includes a central processing unit (“CPU”) 250 operatively coupled to memory 240 which also stores an operating system (not shown) for general management of the client system 210. An example of a suitable client system 210 is an IBM™ ThinkPad™ computer. The client 210 includes computer executable programmed instructions for directing the client 210 to implement the embodiments of the present invention. The programmed instructions may be embodied in one or more software modules resident on the client 210, for example, the UI object interpreter module 260 which will be described below. Alternatively, the programmed instructions may be embodied on a computer readable medium (such as a CD disk or floppy disk), which may be used for transporting the programmed instructions to the memory 240 of the client 210. Alternatively, the programmed instructions may be embedded in a computer-readable, signal-bearing medium that is uploaded to a network 120 by a vendor or supplier of the programmed instructions, and this signal-bearing medium may be downloaded to the client 210 from the network 120 by end users or potential buyers.
  • The CPU 250 of the client 210 is typically coupled to one or more devices (not shown) for receiving user queries or requests and for displaying the results of the queries or requests to users on a display screen. Receiving and displaying of user queries and results of queries is performed through a UI typically presented to the user via a computer screen. The CPU 250 is coupled to memory 240 for containing programs and data. The memory 240 may include a variety of storage devices including internal memory and external mass storage typically arranged in a hierarchy of storage as understood to those skilled in the art.
  • In accordance with the present invention, the UI to be presented to a user via a client 210 is described by server side product code 190 in the server 110 with a UI description 160 and UI dynamic data 170. The product code 190 may be an e-commerce and/or database application, for example. The UI object converter module 180 in the server 110 redefines the UI by breaking the UI into base object components (i.e. UI object definitions). These base object components may be defined in a document such as an Extensible Markup Language (“XML”) document 195, for example. This document may be provided to the client 210 as described further below for rendering the UI.
  • As is known, XML is a flexible way to create common information formats and share both the format and the data on the Web and other networks. XML is a formal recommendation from the World Wide Web Consortium (“W3C”) and is similar to the Hypertext Markup Language (“HTML”). An XML document can be processed purely as data by a program, it can be stored, or it can be displayed like an HTML document. Thus, XML is “extensible” because, unlike HTML, the markup symbols are unlimited and self-defining. In addition, XML markup may appear within an HTML page.
  • Also known, in object-oriented programming (e.g. C++ and Java™), an “object” or “instance of a class” is a unit of computer executable code for implementing a process or task. An object may contain or reference “methods” (also computer executable code) and “data” (e.g. variables) generally shared with other objects in a class of objects.
  • At the client 210, an object interpreter module 270 converts the UI object definitions in the XML document 295 received from the server 110 over the network 120 into UI objects 260 for use by the client 210 to display the actual UI presentation 280 to a user.
  • For example, consider product code 190 having a UI requiring that a Java™ window be displayed to a user at the client 210. According to the present invention, the Java™ objects for the window are defined using an XML document 295 or similar markup language document. The client UI object interpreter module 270 reads the XML document 295 transmitted over the network 120 from the server 110, breaks the document 295 down to construct UI objects 260, and generates the Java™ window UI presentation 280 for display to the user.
  • Advantageously, the use of an XML document 195, 295 allows for improved flexibility. For example, it allows for the creation of instructions (e.g. instantiating an object, invoking a method on an object, etc.), for the creation of operands for these instructions (e.g. object names for method parameters, etc.), and for populating by dynamic data 170.
  • Another advantage of the present invention is that as the maintenance level or version of the product code on the server 190 changes, possibly causing a change to the UI presentation 280 to be displayed to a user at the client 210, it is only necessary to update the server side code (i.e., the UI object converter 180) that builds the XML document 195 that is sent to the client 210. That is, once the object interpreter module 270 is installed on the client 210, no further client side updates are required to receive the synchronized server function.
  • FIG. 2 is a flow chart illustrating operations 300 of modules within a client/server system 100 for synchronizing a client user interface with a backend server in accordance with an embodiment of the invention. At step 301, the operations 300 start.
  • At step 302, a request for a UI presentation 280 to be displayed on the client 210 is made. This request may be initiated either by the user at the client or by the server.
  • At step 303, the request is transmitted to the server 110 where the actual UI description 160 is stored.
  • At step 304, the UI description 160, including any UI dynamic data 170 to be presented in the display to the user, is converted to UI object definitions by the UI object converter module 180.
  • At step 305, the UI object definitions are incorporated in an XML document 195 by the UI object converter module 180.
  • At step 306, the XML document 195 is transmitted to the client 210.
  • At step 307, the UI object interpreter module 270 on the client 210 breaks down the object definitions in the received XML document 295 and converts them into UI objects 260.
  • At step 308, the UI objects 260 are incorporated into a UI presentation 280 for display to the user.
  • At step 309, user input is collected at the client 210, converted into an XML document, and is transmitted to the server 110.
  • At step 310, operations 300 end.
  • While this invention is primarily discussed as a method, a person of ordinary skill in the art understands that the apparatus discussed above with reference to a computer-implemented client/server system may be programmed or configured to enable the practice of the method of the invention. Moreover, an article of manufacture for use with a data processing system, such as a pre-recorded storage device or other similar computer readable medium including program instructions recorded thereon may direct the data processing system to facilitate the practice of the method of the invention. It is understood that such apparatus and articles of manufacture also come within the scope of the invention.
  • The embodiment(s) of the invention described above is(are) intended to be exemplary only. The scope of the invention is therefore intended to be limited solely by the scope of the appended claims.

Claims (21)

1. A server system coupled to at least one client system for synchronizing a user interface (UI) presentation to be displayed to a user of said at least one client system to a UI description maintained by said server system, said server system comprising:
a UI object converter adapted for: (a) converting said UI description into one or more UI object definitions; (b) storing each said UI object definition in a document; and, (c) transmitting said document to said at least one client system; said at least one client system adapted to convert said UI object definitions to UI objects to generate said UI presentation at said client system in synch with said server system.
2. The server system of claim 1 wherein said UI object converter is further adapted for transmitting said document in response to a request for said UI presentation by one or more systems, wherein said systems comprise said at least one client system and said server system.
3. The server system of claim 1 wherein said UI object definitions contain data for said UI presentation.
4. The server system of claim 3 wherein said data contains computer executable code.
5. The server system of claim 3 wherein said data is dynamic data for displaying in said UI presentation.
6. The server system of claim 1 wherein said document is a markup language document.
7. The server system of claim 1 wherein said UI presentation is a graphical user interface (GUI) presentation.
8. A computer program product having a computer readable medium tangibly embodying computer executable code for directing a server system coupled to at least one client system to synchronize a user interface (UI) presentation to be displayed to a user of said at least one client system to a UI description maintained by said server system, said computer program product comprising:
code for converting said UI description into one or more UI object definitions;
code for storing each said UI object definition in a document; and,
code for transmitting said document to said at least one client system; said at least one client system adapted to convert said UI object definitions to UI objects to generate said UI presentation at said client system in synch with said server system.
9. The computer program product of claim 8 wherein said code for transmitting is responsive to a request for said UI presentation by one or more systems, wherein said systems comprise said at least one client system and said server system.
10. The computer program product of claim 8 wherein said UI object definitions contain data for said UI presentation.
11. The computer program product of claim 10 wherein said data contains computer executable code.
12. The computer program product of claim 10 wherein said data is dynamic data for displaying in said UI presentation.
13. The computer program product of claim 8 wherein said document is a markup language document.
14. The computer program product of claim 8 wherein said UI presentation is a graphical user interface (GUI) presentation.
15. An article including a computer readable modulated carrier signal being usable over a network, and means embedded in the computer readable modulated carrier signal for directing a server system coupled to at least one client system to synchronize a user interface (UI) presentation to be displayed to a user of said at least one client system to a UI description maintained by said server system, said article comprising:
means in the medium for converting said UI description into one or more UI object definitions;
means in the medium for storing each said UI object definition in a document; and,
means in the medium for transmitting said document to said at least one client system; said at least one client system adapted to convert said UI object definitions to UI objects to generate said UI presentation at said client system in synch with said server system.
16. The article of claim 15 wherein said means in the medium for transmitting is responsive to a request for said UI presentation by one or more systems, wherein said systems comprise said at least one client system and said server system.
17. The article of claim 15 wherein said UI object definitions contain data for said UI presentation.
18. The article of claim 17 wherein said data contains computer executable code.
19. The article of claim 17 wherein said data is dynamic data for displaying in said UI presentation.
20. The article of claim 15 wherein said document is a markup language document.
21. The article of claim 15 wherein said UI presentation is a graphical user interface (GUI) presentation.
US12/178,598 2003-08-06 2008-07-23 Synchronizing a client user interface with a server backend Abandoned US20080281911A1 (en)

Priority Applications (4)

Application Number Priority Date Filing Date Title
CA2438362 2003-08-06
CA 2438362 CA2438362C (en) 2003-08-26 2003-08-26 A method and system for synchronizing a client user interface with server backend
US10/917,181 US7519739B2 (en) 2003-08-26 2004-08-11 Synchronizing a client user interface with a server backend
US12/178,598 US20080281911A1 (en) 2003-08-06 2008-07-23 Synchronizing a client user interface with a server backend

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US12/178,598 US20080281911A1 (en) 2003-08-06 2008-07-23 Synchronizing a client user interface with a server backend

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US10/917,181 Continuation US7519739B2 (en) 2003-08-26 2004-08-11 Synchronizing a client user interface with a server backend

Publications (1)

Publication Number Publication Date
US20080281911A1 true US20080281911A1 (en) 2008-11-13

Family

ID=34200808

Family Applications (2)

Application Number Title Priority Date Filing Date
US10/917,181 Active 2026-08-07 US7519739B2 (en) 2003-08-26 2004-08-11 Synchronizing a client user interface with a server backend
US12/178,598 Abandoned US20080281911A1 (en) 2003-08-06 2008-07-23 Synchronizing a client user interface with a server backend

Family Applications Before (1)

Application Number Title Priority Date Filing Date
US10/917,181 Active 2026-08-07 US7519739B2 (en) 2003-08-26 2004-08-11 Synchronizing a client user interface with a server backend

Country Status (2)

Country Link
US (2) US7519739B2 (en)
CA (1) CA2438362C (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102376016A (en) * 2010-08-13 2012-03-14 捷达世软件(深圳)有限公司 Process integration server and method for realizing system integration by utilizing same
US8347219B1 (en) * 2010-03-31 2013-01-01 Emc Corporation Object-level display building

Families Citing this family (22)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7899907B2 (en) * 2004-06-30 2011-03-01 Siebel Systems, Inc. Access and synchronization with enterprise applications using remote hosted solution
US20060173928A1 (en) * 2004-12-23 2006-08-03 Ecpg.Net Inc. Method for controlling data review and synchronization
US8527939B2 (en) * 2006-09-14 2013-09-03 Sap Ag GUI modeling of knowledge base in a modeling environment
US9716774B2 (en) * 2008-07-10 2017-07-25 Apple Inc. System and method for syncing a user interface on a server device to a user interface on a client device
WO2010060206A1 (en) 2008-11-26 2010-06-03 Calgary Scientific Inc. Method and system for providing remote access to a state of an application program
SG2014007801A (en) * 2009-02-03 2014-04-28 Calgary Scient Inc Method and system for enabling interaction with a plurality of applications using a single user interface
US10055105B2 (en) 2009-02-03 2018-08-21 Calgary Scientific Inc. Method and system for enabling interaction with a plurality of applications using a single user interface
US8788946B2 (en) * 2009-11-03 2014-07-22 Oracle International Corporation Application agnostic UI integration framework for web based applications
US20110258555A1 (en) * 2010-04-15 2011-10-20 Po-Yen Lee Systems and methods for interface management
CN102404371A (en) * 2010-09-17 2012-04-04 捷达世软件(深圳)有限公司 Simple object access protocol adapter and method thereof for writing file into third party system
US20120166977A1 (en) * 2010-12-27 2012-06-28 Hilmar Demant User programming access to data model in user interface design
US9741084B2 (en) 2011-01-04 2017-08-22 Calgary Scientific Inc. Method and system for providing remote access to data for display on a mobile device
KR20120100045A (en) * 2011-03-02 2012-09-12 삼성전자주식회사 User terminal apparatus, display apparatus, ui providing method and control method thereof
CA2734860A1 (en) 2011-03-21 2012-09-21 Calgary Scientific Inc. Method and system for providing a state model of an application program
WO2013024342A1 (en) 2011-08-15 2013-02-21 Calgary Scientific Inc. Method for flow control and for reliable communication in a collaborative environment
SG10201606764XA (en) 2011-08-15 2016-10-28 Calgary Scient Inc Non-invasive remote access to an application program
EP2761808A4 (en) 2011-09-30 2015-05-20 Calgary Scient Inc Uncoupled application extensions including interactive digital surface layer for collaborative remote application sharing and annotating
CA2865707A1 (en) 2012-03-02 2013-09-06 Calgary Scientific Inc. Remote control of an application using dynamic-linked library (dll) injection
US9729673B2 (en) 2012-06-21 2017-08-08 Calgary Scientific Inc. Method and system for providing synchronized views of multiple applications for display on a remote computing device
CN105765923A (en) 2013-11-29 2016-07-13 卡尔加里科技股份有限公司 Method for providing a connection of a client to an unmanaged service in a client-server remote access system
CN104202335B (en) * 2014-09-19 2018-04-20 成都博智维讯信息技术有限公司 A simplified sap-based data transmission method xml
US10015264B2 (en) 2015-01-30 2018-07-03 Calgary Scientific Inc. Generalized proxy architecture to provide remote access to an application framework

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020120679A1 (en) * 2000-12-12 2002-08-29 Richard Hayton Methods and apparatus for communicating changes between a user interface and an executing application using property paths
US6636897B1 (en) * 1999-09-28 2003-10-21 Microsoft Corporation Selective information subset synchronization based on single user action
US7627658B2 (en) * 2001-02-12 2009-12-01 Integra Sp Limited Presentation service which enables client device to run a network based application

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5517645A (en) * 1993-11-05 1996-05-14 Microsoft Corporation Method and system for interfacing components via aggregate components formed by aggregating the components each with an instance of a component manager
US5802531A (en) 1995-05-08 1998-09-01 Apple Computer, Inc. Method and system for embedding parts of documents and synchronizing multiple views thereof
JPH11191062A (en) 1997-12-26 1999-07-13 Hitachi Ltd Application image development support system
US6023271A (en) 1998-06-11 2000-02-08 Sun Microsystems, Inc. Framework for binding data viewers/data manipulation with one to many objects through introspection
AU4202701A (en) 2000-03-08 2001-09-17 Marbles Inc Remote operation of real-time graphical applications
SE517132C2 (en) * 2000-06-27 2002-04-16 Printon Ab Method and system for creating a PDF document
AU2002237756A1 (en) 2001-01-04 2002-07-16 3Cx, Inc. Synchronized multimedia presentation
JP2003150586A (en) * 2001-11-12 2003-05-23 Ntt Docomo Inc Document converting system, document converting method and computer-readable recording medium with document converting program recorded thereon
JP2004094487A (en) * 2002-08-30 2004-03-25 Matsushita Electric Ind Co Ltd Support system for preparing document

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6636897B1 (en) * 1999-09-28 2003-10-21 Microsoft Corporation Selective information subset synchronization based on single user action
US20020120679A1 (en) * 2000-12-12 2002-08-29 Richard Hayton Methods and apparatus for communicating changes between a user interface and an executing application using property paths
US7627658B2 (en) * 2001-02-12 2009-12-01 Integra Sp Limited Presentation service which enables client device to run a network based application

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8347219B1 (en) * 2010-03-31 2013-01-01 Emc Corporation Object-level display building
CN102376016A (en) * 2010-08-13 2012-03-14 捷达世软件(深圳)有限公司 Process integration server and method for realizing system integration by utilizing same

Also Published As

Publication number Publication date
CA2438362A1 (en) 2005-02-26
US7519739B2 (en) 2009-04-14
US20050050229A1 (en) 2005-03-03
CA2438362C (en) 2011-05-31

Similar Documents

Publication Publication Date Title
EP0747845B1 (en) Computer network for WWW server data access over internet
US8321450B2 (en) Standardized database connectivity support for an event processing server in an embedded context
US7103836B1 (en) Method and system for generating materials for presentation on a non-frame capable web browser
US7092936B1 (en) System and method for search and recommendation based on usage mining
US5737592A (en) Accessing a relational database over the Internet using macro language files
US5710918A (en) Method for distributed task fulfillment of web browser requests
US5701451A (en) Method for fulfilling requests of a web browser
US6134549A (en) Client/server computer system having personalizable and securable views of database data
US5781739A (en) IMS/WWW mapping system
US7194485B2 (en) Mapping XML schema components to qualified java components
US7310639B2 (en) Providing query correlation attributes
US7454479B2 (en) Flexible teleport architecture
EP0986788B1 (en) Web server mechanism for processing function calls for dynamic data queries in a web page
US7640239B2 (en) Methods and apparatus for real-time business visibility using persistent schema-less data storage
US6324568B1 (en) Method and system for distributing objects over a network
US8069223B2 (en) Transferring data between applications
US8131744B2 (en) Well organized query result sets
EP1361509B1 (en) Software delivery manager
US7373351B2 (en) Generic search engine framework
US6757868B1 (en) Programmatic switching of arbitrary HTML forms
US6424966B1 (en) Synchronizing crawler with notification source
US7233940B2 (en) System for processing at least partially structured data
US7444643B2 (en) Accessing a ERP application over the internet using strongly typed declarative language files
US6240417B1 (en) Integration of legacy database management systems with ODBC-compliant application programs
US6920461B2 (en) Application program interface for network software platform

Legal Events

Date Code Title Description
STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION