US20090007160A1 - System and method for network-based computing - Google Patents

System and method for network-based computing Download PDF

Info

Publication number
US20090007160A1
US20090007160A1 US12/209,826 US20982608A US2009007160A1 US 20090007160 A1 US20090007160 A1 US 20090007160A1 US 20982608 A US20982608 A US 20982608A US 2009007160 A1 US2009007160 A1 US 2009007160A1
Authority
US
United States
Prior art keywords
markup
client
application program
business logic
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/209,826
Inventor
Coach K. Wei
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.)
Nexaweb Tech Inc
Original Assignee
Nexaweb Tech Inc
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
Application filed by Nexaweb Tech Inc filed Critical Nexaweb Tech Inc
Priority to US12/209,826 priority Critical patent/US20090007160A1/en
Publication of US20090007160A1 publication Critical patent/US20090007160A1/en
Assigned to MONTAGE CAPITAL, LLC reassignment MONTAGE CAPITAL, LLC SECURITY AGREEMENT Assignors: NEXAWEB TECHNOLOGIES, INC.
Assigned to NEXAWEB TECHNOLOGIES, INC. reassignment NEXAWEB TECHNOLOGIES, INC. RELEASE BY SECURED PARTY (SEE DOCUMENT FOR DETAILS). Assignors: MONTAGE CAPITAL, LLC
Abandoned legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/40Transformation of program code
    • G06F8/41Compilation
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/14Session management
    • H04L67/142Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms

Definitions

  • the present invention relates to a system and a method for network-based computing, and more particularly, to network-based computing that provides network applications that can be automatically deployed, compiled, and executed by any type of a client machine connected to a server via any type of a network connection.
  • a typical computing system includes hardware and software components.
  • Hardware components include computing devices such as personal computers (PC), mainframe computers, and computing circuits, among others.
  • the basic architecture of a computing device includes a central processing unit (CPU), which executes instructions, and a memory unit, which stores instructions and data. Instructions and data are transmitted from the memory unit to the CPU and the results of the CPU operations are sent back to the memory unit.
  • Software components are application programs, which contain the set of instructions that are executed by the CPU unit. Application programs include among others, system programming software, drawing software, word processing software, spreadsheet evaluation software, enterprise resource management software, customer relationship management software, data analysis software, customer self-help software, network and storage management software, mathematical and scientific software.
  • a computer programmer develops an application program by first coding a set of instructions in a source file using the grammar rules of a programming language.
  • a programmer writes a source file using the grammar and syntax of the JavaTM programming language 82 .
  • the JavaTM source file passes through a JavaTM compiler 84 where it gets analyzed and parsed.
  • the parsed file is then used to generate a JavaTM bytecode 86 , i.e., a code that is understood by a JavaTM Virtual Machine (JVMTM).
  • JVMTM JavaTM Virtual Machine
  • the computing device retrieves the compiled JavaTM bytecode file 86 from the memory, the JavaTM Virtual Machine 88 executes it, and the computing results are displayed 89 .
  • the compiled JavaTM bytecode file 86 may also be stored in a computer readable storage medium such as a compact disk (CD) or a magnetic floppy disk or tape. These computer readable storage media may also be used to distribute and install the application program, i.e., the compiled JavaTM bytecode files, in other computing devices. This computing system is sufficient for independent computing devices.
  • a network-based computing system includes a central server and a plurality of computing devices, i.e., client machines, that are connected with each and to the server via a network.
  • Application programs are stored in the central server and can be deployed to the client machines via the network. Alternatively, application programs can be installed in the client machines via a manual distribution of computer readable media such as CD or floppy disks containing the compiled application code.
  • Network-based computing is used for large enterprises that have multiple computing devices in multiple locations that interact with each other and with the server via a network connection.
  • An application program in the network-based computing system includes a server program that is stored in the server and a client program that is stored in the memory of a client machine. The server program runs on the server and the client program runs on one of the client machines.
  • a financial services company may utilize an internal Investment Portfolio Management application to perform stock analysis.
  • a portfolio manager wants to do a specific stock analysis, he starts the client program for the Investment Portfolio Management application in the client machine.
  • the client machine loads the multi-megabyte client program, and then receives and processes the portfolio manager's requests.
  • the client machine may also send further requests to the server program via the network to gather any necessary data.
  • the client program receives the necessary data, analyzes the data and presents the result in an appropriate format to the portfolio manager.
  • Processes associated with network-based computing include application development, application deployment, and application execution, among others.
  • Application development refers to the coding, compiling, and debugging of the server and client programs that can be run by the server and the various configurations and operating systems of the client machines, respectively.
  • Application deployment refers to the distribution and installation of the various client programs in the various client machines.
  • Application execution refers to the execution of the compiled server and client programs by the server and the various client machines of the network, respectively.
  • Client platform incompatibilities include different operating systems and different hardware.
  • the operating systems may be various versions of Windows, Mainframe, Macintosh, Unix, Linux, and PalmTM.
  • the different hardware may be Pocket PCs, desktops, laptops, workstation, phone systems, personal digital assistants (PDA) and smart television sets.
  • Device configuration includes the specific settings that a given application may require, such as the Dynamic Link Library (DLL) version and registry for typical Windows applications.
  • DLL Dynamic Link Library
  • client platform and device configuration incompatibilities result in a significant amount of complexity and increased costs for the development of network applications.
  • client program execution requires loading almost the entire program into memory before the user is able to run the application.
  • client programs are typically multi-megabyte files and loading such big files into memory creates lengthy delays for users.
  • this execution model creates increasing demands on hardware because it requires faster CPU, bigger memory, more storage, and a faster network, all of which translate into costs and performance issues.
  • JavaTM Applet approach Alternative approaches to this static network-based computing system include the JavaTM Applet approach and the Hyper Text Markup Language (HTML) web page approach.
  • JavaTM Applet approach the client component of a network application is written as a JavaTM Applet, and the end users can access this application without the need to install it in advance.
  • JavaTM Applets have severe technical limitations that restrict its practical use to simple application only. For complex enterprise applications, the JavaTM Applet not only performs poorly but also can easily have a footprint in excess of 1 MB, which requires lengthy downloading which in turn effectively prevents users from using it over the Internet or WAN.
  • JavaTM Applets require a JavaTM Virtual Machine (JVMTM) on the client machine.
  • JVMTM JavaTM Virtual Machine
  • HTML web page approach companies use HTML for publishing simple application screens.
  • the entire application is running on the server.
  • Each screen is formatted into an HTML web page and displayed in a web browser.
  • Some simple client-side logic can be added to the HTML page using technologies, such as JavaScriptTM.
  • this approach is limited to applications that require minimal user interactivity and functionality.
  • Network applications using this approach sacrifice many of the features and functionality associated with client-side computing, such as offline computing, drag&drop, multiple windows, spreadsheet behavior, among others.
  • the “click and refresh” user interaction model associated with web browsing is not suitable for network applications because this model not only consumes significant bandwidth by sending and re-sending redundant information, but it also significantly lowers user productivity by keeping users waiting with every mouse click.
  • the client-side business logic is also limited because a scripting language, such as JavaScriptTM, does not scale well to a large team of developers, unlike the more robust Object-oriented programming (OOP) languages like JavaTM and C++.
  • OOP Object-oriented programming
  • HTML is used only for simple applications. Important applications are still being written as traditional Client/Server applications using OOP languages.
  • the invention features a computer application program including at least one markup document, at least one business logic component associated with and applied directly to the at least one markup document and an object oriented binding mechanism binding the at least one markup document to the at least business logic component and the reverse.
  • a client runtime environment may receive and convert the at least one markup document into an object-oriented representation.
  • the object-oriented representation may include one or more markup objects, one or more user interfaces, and one or more data sets.
  • the at least one business logic component may include one or more methods used as event handlers for a markup object event.
  • the object oriented binding mechanism may include invoking the one or more methods by the one or more markup objects by firing a markup object event.
  • the object oriented binding mechanism may further include accessing and modifying the one or more markup objects by the at least one business logic component via an Application Program Interface (API).
  • API Application Program Interface
  • the API may be a markup object API or a Document Object Model (DOM) API.
  • the one or more markup objects may include a parent markup object and a child markup object and the child markup object may have one or more markup object properties inherited from the parent markup object.
  • the one or more markup object properties may be a user interface definition, a data set definition or an event handler definition.
  • the parent markup object may have one or more user interface definitions, one or more data definitions and one or more event handlers and the child markup object may inherit the one or more user interface definitions, the one or more data definitions and the one or more event handlers from the parent markup object.
  • the one or more markup objects may include a parent markup object and a child markup object and the child markup object may overwrite one or more markup object properties of the parent markup object and replace them with one or more markup object properties of the child markup object.
  • the at least one markup document may be written in a markup language including among others, XML, XUL, SVG, Xforms, XAML, HTML, HTML related languages, text, or combinations thereof.
  • the one or more business logic components may be written in a programming language including among others, JavaTM, JavaScriptTM, J#, C#, C+, C++, Visual Basic, ActionScript, XSL, XQuery, or XPath.
  • the invention features a network application program having one or more modules wherein each module includes at least one markup document, at least one business logic associate with the at least one markup document and an object oriented binding mechanism binding the at least one markup document to the at least business logic component and the reverse.
  • the invention features a method of binding a markup document with one or more business logic objects including coding the markup document using a markup language, coding the one or more business logic objects using an object oriented programming language and associating the markup document with the one or more business logic objects.
  • constructing an object oriented representation of the markup document thereby generating one or more markup objects.
  • firing one or more markup object events by the object oriented representation thereby invoking the one or more business logic objects for processing the events and finally manipulating the markup objects by the one or more business logic objects.
  • the business logic objects may manipulate the markup objects via a markup object API or a Document Object Model (DOM) API.
  • the computing system enables partitioned delivery and execution of a network application from a central server to any client machine connected to the server via a network connection.
  • the network connection may be a low bandwidth network.
  • the client machines may include any type of computing platforms and devices.
  • the network application includes markup documents, business logic components and an object-oriented binding mechanism binding the markup documents to the business logic components and the reverse.
  • the markup documents may be scripted using any type of a markup language including among others, XML, XUL, SVG, Xforms, XML related languages, HTML, HTML related languages, text, and combinations thereof.
  • the business logic components may include source code scripted in any programming language including among others, JavaTM, JavaScriptTM, J#, C#, C+, C++, Visual Basic, ActionScript, XSL, XQuery, and XPath.
  • a compiler system converts the source code to any type of executable bytecode. This compiler system configuration provides flexibility in both the programming side of the application and the execution side of the application.
  • FIG. 1 is a block diagram of a prior art process for writing, compiling and executing of an application
  • FIG. 2 is an example of a network-based computing system
  • FIG. 3 is a block diagram of the software and hardware components of a simple network-based computing system
  • FIG. 4 is a schematic diagram of the server compiler of the application server of FIG. 3 ;
  • FIG. 4A is a detailed block diagram of the universal JavaTM bytecode compiler of FIG. 4 ;
  • FIG. 4B is a detailed block diagram of the universal XML compiler of FIG. 4 ;
  • FIG. 5 is a block diagram of an object-oriented application according to this invention.
  • FIG. 6 is a schematic diagram of the markup-business logic binding mechanism of this invention.
  • FIG. 7A-FIG . 7 B are code examples of the markup-business logic binding mechanism
  • FIG. 7C is a screen shot of the example of FIG. 7A ;
  • FIG. 7D is another screen shot of the example of FIG. 7A ;
  • FIG. 8 is a schematic diagram of the object-oriented markup object declaration and instantiation
  • FIG. 9 is a schematic diagram of the module structure of a network-based application according to this invention.
  • FIG. 10 is a flow diagram of the process of deploying, compiling and executing a network-based application according to this invention.
  • FIG. 11 is a flow diagram of the event handing process of this invention.
  • a network-based computing system 70 includes a server 72 and client machines 73 , 74 , 75 , and 76 .
  • the client machines include a personal computer 73 , a laptop computer 74 , other computing devices 75 , and a wireless communication device 76 .
  • Client machines 73 , 74 and 75 are connected to the server 72 via a network connection 78 .
  • Client machine 76 is connected to the server 72 via a wireless network connection 79 .
  • There may be several additional client machines including personal computers, laptop computers, Linux machines, workstations, computing circuits, and wired communications devices, such as telephone and television.
  • Network connection 78 may be the Internet, the World Wide Web (WWW), a Wide Area Network (WAN), a Local Area Network (LAN), a Personal Area Network (PAN) or a telecommunication network.
  • the wireless communication device 76 may be a mobile phone, a personal digital assistant (PDA), a pager, a wireless laptop computer, a personal computer, a television, and programmable versions thereof or combinations thereof.
  • the wireless network 79 may be a wireless wide area network (WWAN), a wireless local area network (WLAN), a wireless personal area network (WPAN) or a private communication network.
  • a block diagram of the software and hardware components of a simple network computing system 200 includes an application server 210 , a client machine 220 , and a web server 219 .
  • the application server 210 runs behind the web server 219 , and runs server-side application code (or server-side business logic) 212 .
  • the web server 219 delivers markup documents or electronic messages generated by the server side application code 212 to a client web browser 230 residing inside the client machine 220 .
  • Electronic messages are communication messages delivered electronically for information exchange.
  • Markup documents are electronic documents, i.e., files, written using a markup language such as XML or HTML.
  • a markup language is a conventional language for describing the contents of an electronic document that is to be viewed or printed on a computer output device such as a computer monitor.
  • a markup language document can contain text, images, JavaScriptTM, and hyperlinks, among others.
  • a real time, bidirectional, reliable messaging system 240 transmits messages between the client web browser 230 and the web server 219 over an HTTP web connection.
  • the application server includes in addition to the server side application code 212 a Server Runtime Environment (SRE) 214 .
  • the SRE 214 runs behind the HTTP web server 219 and inside the application server 210 .
  • the SRE 214 includes a server compiler 216 , a server cache 218 , a communications module 215 , and other functional modules 217 .
  • the functional modules 217 include an Application Server Interface, an XML Parser, Clustering, Storage, and an Execution Engine.
  • the application server interface module enables the SRE 214 to run inside the application server 210 and enables applications inside the application server 210 to access the SRE's functionalities.
  • the XML Parser module is responsible for parsing XML documents that come from the various client machines or other information sources such as other backend connections. The parsing results may be stored in the Storage module.
  • the clustering module provides support for clustering the SRE and the execution engine module executes the compiled server-side application code 212 .
  • the client machine 220 includes a client runtime environment (CRE) 224 that runs outside the client web browser 230 and client-side application code 222 (or client-side business logic). In other embodiments the CRE runs inside the client web browser 230 .
  • the client side application code 222 includes Extensible Markup Language (XML) documents and procedural code.
  • the client machine 220 is protected by a client side firewall 244 and the web server 219 is protected by a server side firewall 242 .
  • the CRE 224 processes markup documents and executes the client-side application code 222 .
  • the CRE 224 includes a client cache 226 , a communication module 225 , a state synchronization and persistency module 228 and other functional modules 227 such as an XML parser, a user interface, storage, security, and an execution engine.
  • the XML Parser is responsible for parsing XML documents that come from the application server 210 .
  • the parsing results may be stored in the client cache 226 as part of the application's client side state.
  • the user interface module is responsible for displaying the user interface and interacting with the user according to the application's XML description.
  • the execution engine module is capable of running client side application code 222 .
  • the client cache 226 maintains the application's client side state and is updated by the CRE automatically.
  • the synchronization and persistency module 228 is responsible for synchronizing the client cache 226 with the application server 210 , and saving and/or retrieving the client cache 226 from persistent storage.
  • the CRE 224 is centrally managed by the SRE 214 .
  • the CRE 224 is automatically downloaded from the application server 210 and installed in the client machine 220 the first time a user access a client application. After the initial installation, the SRE 214 automatically manages the versioning and updating of the CRE 224 .
  • Different CREs 224 are used for the different client platforms. For example, different CREs are used for a JavaTM Virtual Machine, a NET CLR, or a Flash Player.
  • the executable application code formats of these three client platforms are: JavaTM bytecode, .NET CLR bytecode and Flash bytecode, respectively.
  • the application code 222 is delivered in three different executable code formats for these three client platforms, accordingly.
  • the server compiler 216 is a software program that translates source code written in any supported programming language into executable code of any supported executable format.
  • the source code is written in a programming language, such as JavaTM, C#, JavaScriptTM, and XML, among others.
  • the supported executable formats are JavaTM bytecode, .NET CLR bytecode, or Flash bytecode, among others, depending on the client platform. For example, when the client platform is running a JavaTM Virtual Machine 360 , all input source files, no matter which language they are being written in, are compiled into JavaTM bytecode executable files by the server compiler 216 . Similarly, if the client platform is running a .NET CLR, all source code files are compiled into .NET CLR bytecode.
  • the server compiler 216 includes a plurality of specific universal compilers including among others, a universal JavaTM Bytecode compiler 312 , a universal .NET CLR (Common Language Runtime) compiler 314 , a universal JavaScriptTM compiler 316 , a universal Flash SWF compiler 318 , and a universal XML compiler 320 .
  • the server compiler 216 also includes a server compiler control logic 310 that detects the type of the client platform, invokes compiling and caching of a client platform appropriate executable code and delivers the appropriate executable code to the corresponding client platform.
  • the control logic 310 first characterizes the client machine to see which executable format is supported by this client machine.
  • the server compiler control logic 310 sends the cached executable code to the client machine directly. If the source file has been changed since the last compilation, the control logic 310 prompts the server compiler 216 to retrieve the source file, compile the source file into the appropriate executable code, cache the executable code in the server cache 218 and send the executable code to the client machine.
  • Each universal compiler receives an input file written in any programming language, such as JavaTM, C#, JavaScriptTM, C+, C++, Visual Basic, and delivers an output file in one executable format specific to a certain client platform.
  • the input files 302 , 304 , 306 and the output files 332 , 334 , 336 , 340 may also include markup documents written in XML.
  • the universal JavaTM bytecode compiler 312 receives source code files written in programming languages such as JavaTM 302 , C# 304 , JavaScriptTM 306 , among others, and delivers a JavaTM Virtual Machine executable JavaTM bytecode file 332 .
  • the universal JavaTM bytecode compiler 312 includes a plurality of custom developed language compilers, such as JavaScriptTM compiler 353 , a plurality of commercially available language specific compilers, such as JavaTM compiler 351 , J# compiler 352 , C# compiler, among others, and a control logic 355 .
  • JavaTM compiler 351 is commercially available from Sun Microsystems of Santa Clara, Calif.
  • J# compiler 352 is commercially available from Microsoft of Redmond Wash.
  • the JavaScriptTM compiler 353 is custom developed by Nexaweb and compiles JavaScriptTM files into JavaTM bytecode.
  • the universal .NET CLR compiler 314 receives input files written in any programming language and deliver bytecode files executable by a .NET CLR engine, a JavaScriptTM engine, and a Flash player, respectively.
  • the control logic 355 module includes rules for handling the various programming language codes and processes the input files. When an input file is received, control logic module 355 checks which language the source code file is being written in and selects the appropriate language specific compiler to compile the source code file into executable code in the desired executable format. For example, control logic 355 of the Universal JavaTM bytecode compiler 312 would select the JavaScriptTM compiler 353 to compile JavaScriptTM source files and JavaTM compiler 351 to compile JavaTM source files.
  • the universal XML compiler 320 receives files written using various markup languages such as, XHTMLTM ( 362 ), x-Forms ( 364 ), HTML ( 365 ), XAML ( 370 ), SVG ( 368 ), and delivers XML code ( 340 ) executable by an XML execution engine ( 366 ).
  • the universal XML compiler 320 includes a plurality of markup language specific compilers, such as XHTMLTM compiler 371 , XAML compiler 372 , SVG compiler 373 , among others, and a control logic 355 .
  • the control logic 355 is responsible for selecting and invoking a markup language specific compiler to compile a source file written in the specific markup language.
  • the language specific compiler takes the markup document and converts it into a new markup document in the executable format required by the execution engine. For example, if the execution engine is a SVG rendering engine that knows how to render SVG and the source code file is written using XAML, the XAML compiler takes the XAML input and converts it into SVG format. This compilation process can be achieved using an XML Stylesheet Transformation (XSLT), or some other lexical analysis and transformation.
  • XSLT XML Stylesheet Transformation
  • the compiled bytecode files 332 , 334 , 336 , 340 may be stored in the server cache 218 , shown in FIG. 4 .
  • the SRE 214 determines the particular executable format of the CRE 224 and checks if this particular format has already been compiled and is stored in the server cache 218 . If the particular compiled bytecode exist in the server cache 218 and the code has not been modified since the last time it was compiled the SRE 214 downloads the executable file to the CRE 220 an stores it in the client cache 226 . Otherwise, the SRE 214 will invoke the server compiler 216 , and first compile the requested code in the particular executable format and then download it to the CRE 224 and store it in the client cache 226 .
  • This invention utilizes object-oriented programming methodology to develop object-oriented application programs.
  • Object-oriented application programs typically model a problem using an “object model” that defines classes of objects representing elements of the problem.
  • a class of objects is defined in terms of the relationship of the class to other classes, the data and properties (or attributes) associated with objects in the class, and the operations (or tasks) that can be performed on objects in the class.
  • instances of the classes in the object model referred to as “objects”
  • Computation on these “objects” is performed by calling on “methods” defined in business logic components associated with these “objects”. For example, in an accounting management program, the various accounts are defined as the program objects.
  • Each object i.e., account
  • Tasks associated with these account objects may be “get account number”, “set account name”, “set account amount”, among others.
  • Objects interact with each other and with the business logic code via events or messages. An object may fire an event (or send a message) in order to modify its own properties, or state. Events are received and processed by the subprograms or business logic components associated with these objects.
  • Object-oriented programming languages are well known in the art and are described in “Programming languages” Chapter 11, p 435-483, edited by Robert W. Sebesta.
  • the object-oriented application code 400 includes one or more markup documents 402 and one or more business logic components 406 .
  • the markup documents 402 are files written using an XML markup language.
  • the business logic components 406 include instructions for performing tasks upon the program objects. These instructions are formulated as source code files written in a programming language, such as JavaTM, JavaScriptTM, C#, Visual Basic (VB), J#, among others.
  • the business logic components 406 are also program objects.
  • the Client Runtime Environment (CRE) 224 receives the markup documents 402 and converts them into object-oriented representations, i.e., markup objects 404 .
  • the markup objects 404 may be user interfaces (UI) 401 or data 403 .
  • Each markup object 404 may have events associated with it. For example, in the case of a UI markup object that has input fields or buttons, an event may include highlighting the button or input field, entering text in the field, or clicking the button, among others. The event is received and processed by the business logic component, so that the state of the object is modified. In the example of the user interface with the input fields, where text is entered in the input fields, the business logic component modifies the UI to display the entered text.
  • the object oriented representations of the markup documents 405 and business logic components 406 are bound via a markup-business logic binding mechanism 500 .
  • the markup-business logic binding 500 includes the process of binding the markup objects to the business logic components ( 520 ) and the process of binding the business logic components to the markup objects ( 530 ).
  • markup objects 510 defined in markup document 550 invoke business logic components 540 by firing markup object events 521 .
  • the business logic components 540 include definitions of methods that are used as the event handlers for the markup object events.
  • the CRE invokes the associated method in the corresponding business logic component, passes necessary information about the event to the method and executes the method.
  • firing an event may be entering a user's phone number in the appropriate input field.
  • the business logic component receives this markup object event, validates it and formats the phone number for display.
  • business logic components 540 can access and modify the markup objects 510 via a markup object Application Program Interface (API), or a Document Object Model (DOM) API, 531 .
  • API markup object Application Program Interface
  • DOM Document Object Model
  • the CRE 224 parses and stores the markup document 550 into a DOM, and exposes this DOM as a set of API that can be invoked by business logic components 540 .
  • Business logic components 540 invoke this DOM API to programmatically manipulate the markup document 550 stored in the DOM.
  • This feedback mechanism via the markup object API 531 may be “a form validation” process or an internal calculation that will result in modifying the markup objects 510 .
  • a “form validation” process the user enters in the UI a phone number that has three digits.
  • the business logic component recognizes that a three digit phone number is not valid, rejects the input, displays an error in the UI and requests a valid phone number.
  • This two-way binding mechanism 500 enables the clear separation of business logic, presentation and data.
  • the HTML and JavaScriptTM interaction models in web browsers share a similar architecture.
  • the present invention differs from these prior art models because it allows for object-oriented binding.
  • the markup documents are converted into object oriented representations (markup objects) and the business logic components become program objects as well.
  • the object-oriented binding is then a binding between these objects, i.e., the markup objects and the program objects.
  • the business logic is written as scripts, which are not object oriented, and the binding is a binding between program methods to HTML objects.
  • This object-oriented binding of this invention allows for the development of complex applications and provides programming language and execution format independence.
  • the business logic code may be written in any programming language including JavaTM, JavaScriptTM, C#, J#, VB, and C+
  • the markup documents may be written in any markup language including XML, text, and HTML, among others.
  • the programming language is not object oriented
  • the source code can be compiled by the universal compiler into an object oriented executable code.
  • XML specifications may be used including XUL (XML User Interface Language), SVG (Scalable Vector Graphics) and XForms. The combination of these XML languages creates a rich environment that supports all functionalities of all network applications including typical Windows graphical user interface, forms, 2D graphics and animation.
  • a code example 600 of the markup-business logic binding mechanism 500 is shown in FIG. 7A and FIG. 7B .
  • a markup document 610 is written using XML.
  • the markup document 610 defines a client-side logic object “bean 1 ” 621 , a parent button “parentBtn” 632 , a child button “childBtn” 635 , and a data object “companyInfo” 641 .
  • the client-side logic object “bean 1 ” 621 defines a client-side programming object whose source code is “com.nexaweb.clientbean.DemoBean”, effectively associating the business logic component 650 with this markup document 610 .
  • the source code for business logic component 650 is written using the JavaTM programming language and defines a JavaTM class with three different methods, including “init” 660 , “doClick” 670 , and “doOver” 680 .
  • the markup document to business logic binding 520 is achieved by using the three methods 660 , 670 , 680 of the business logic component 650 as the event handlers for events fired by the three markup objects 621 , 632 , and 635 , respectively.
  • Method 660 processes the “onload” event for markup object 621
  • method 670 processes the “oncommand” event for the parent button 633
  • method 680 processes the “onmouseover” event for the child button 635 .
  • the CRE invokes the corresponding method in the business logic component to process it.
  • An example of the business logic to markup binding 530 is shown in the implementation of the three methods 660 , 670 , 680 in the business logic component 650 .
  • the “doClick” method 670 inspects the event information, retrieves the event source, which should be the markup object that the user clicked, and sets the “text” attribute of this markup object to be the processed result. For example by clicking on the parent button object 632 the text “You clicked button: parentBtn” appears on the UI screen 633 , as shown in FIG. 7C . Similarly, by clicking on the child button object 635 the text “You clicked button: childBtn” appears on the UI screen 636 , as shown in FIG. 7D .
  • FIG. 8 shows how this invention allows object-oriented markup object inheritance. This process greatly simplifies the creation and management of markup documents and increases the flexibility of markup documents.
  • the parent markup object 710 includes a user interface definition 720 , an object specific data definition 730 and object behavior (or event handler) definition 740 .
  • the child markup object 750 includes a user interface definition 760 , an object specific data definition 770 and object behavior (or event handler) definition 780 .
  • the child markup object 750 inherits all these UI, data and behavior definitions 760 , 770 and 780 , respectively, from the parent markup object 710 .
  • the child markup object 750 can also optionally overwrite the corresponding parent definitions and add new definitions.
  • This object-oriented approach allows for inheriting and changing not only object attributes, but also allows for entire different object behavior by replacing the parent object's event handler definition with child specific event handlers.
  • the “childBtn” 635 inherits all definitions (UI, data and behavior) from the “parentBtn” 632 .
  • markup object specific data are changed, i.e., the “id” is changed from “parentBtn” to “childBtn”.
  • the user interface definition is changed, i.e., the value of “text” attribute is changed so that the text “You clicked button: childBtn” is displayed instead of “You clicked button: parentBtn”.
  • the “childBtn” inherits the object behavior from “parentBtn” so that the “oncommand” event will invoke the “bean 1 .doClick ( )” method 670 for the child markup object, as well.
  • the child markup object 750 also modifies the behavior definition of the parent markup object 710 by binding the “bean 1 .doOver ( )” method 680 to the “onmouseover” event so that the “onmouseover” event will invoke the “bean 1 .doOver ( )” method 680 for the parent markup object, as well.
  • application code 400 includes N number of modules, Module 1 ( 410 ), Module 2 ( 450 ), Module 3 ( 480 ), . . . Module N (not shown). Each module includes one or more markup documents and optionally one or more business logic components. In the example of FIG.
  • Module 1 ( 410 ) includes a markup document 420 and business logic components A ( 430 ) and B ( 440 ).
  • Markup document 420 defines two markup objects, i.e., a User Interface (UI) 422 and a Data file 424 .
  • Module 2 ( 450 ) includes a business logic component C ( 470 ) and a markup document 460 defining a User Interface 462 and a Data file 464 .
  • Module 3 ( 480 ) includes business logic component A ( 430 ), business logic component E ( 494 ) and a markup document 490 defining a User Interface 492 and a Data file 493 .
  • Different modules may share business logic components.
  • Module 3 uses the same business logic component A ( 430 ) as Module 1 ( 410 ).
  • the system 200 of FIG. 3 uses client-side caching 226 , as well as server-side caching 216 to avoid loading the same module or component more than once.
  • each module may require only one XML document and a few compiled business logic components, therefore resulting in a small footprint for each module.
  • This small footprint of each module enables fast application code downloading.
  • the server also provides for automated updating of the modules that were previously downloaded in the client machine and were stored in the client cache.
  • the process 800 of running and application through a client machine includes the following steps.
  • a user wants to use a network application he starts the CRE and enters a request to start the client program ( 802 ).
  • the CRE receives the request ( 804 ) and checks to see if the initial module is available in the local client cache ( 806 ). If the module is not available in the local cache ( 807 ), the CRE sends a request to the server (SRE) to download the specific module ( 808 ).
  • the server delivers the markup document that describes the specific module to the CRE ( 810 ) and the CRE inquires if this markup document needs to be cached ( 812 ) by checking the document properties or configuration information.
  • the CRE caches it in the local client cache ( 814 ) and then proceeds to the next question ( 815 ). Similarly, if the markup document does not need to be cached in the local client cache ( 811 ), the CRE proceeds to the next question ( 815 ). If the module is available in the local cache ( 809 ), the CRE skips the downloading process and proceeds to the next question ( 815 ), as well. Next, the CRE checks the module properties or configuration information to see if this module requires a business logic component ( 816 ). If no business logic component is required ( 815 ) the CRE displays the module to the user ( 818 ) and then waits for a user input ( 820 ).
  • process ( 840 ) takes place.
  • the CRE proceeds to check if the business logic component is available in the local cache ( 824 ). If the business logic component is available in the local cache ( 821 ), it gets loaded from the local cache ( 826 ) in the active memory. If the business logic component is not locally available ( 823 ), the CRE sends a request to the server to download the business logic component ( 828 ). The server checks if this business logic component has been compiled before for this particular client machine executable format ( 830 ), and if it has ( 831 ) it downloads the executable code from the server cache to the client cache ( 834 ).
  • the CRE stores the executable code in the client machine cache ( 836 ) and loads it in the active memory ( 826 ). If the business logic component has not been previously compiled for the specific client machine executable format ( 829 ), the server first compiles it into an executable code executable by the specific client machine execution engine and stores it in the server cache ( 832 ). Next, the server downloads the executable code from the server cache to the client cache ( 834 ), where the CRE caches it in the client cache ( 836 ) and then loads it in the active memory ( 826 ). Finally, both the markup document and the business logic component ( 837 ) are present in the active memory and wait for an input from the user ( 820 ).
  • the process ( 840 ) is repeated for each individual business logic component ( 841 ).
  • the process 800 is repeated for downloading the next module and the business logic components that are associated with it.
  • the CRE receives the markup language document, it immediately processes the document, executes the associated business logic and displays the result to the user.
  • This module-type downloading and execution of a network application has the advantages of being fast and requiring low bandwidth.
  • the storing of the previously downloaded modules and associated business logic in the client-side cache and the server cache and the synchronization of the client-side cache with the server cache allows the client machine to execute the network application offline, even in the case when the network connection is not available.
  • FIG. 11 depicts how the system handles the client events ( 900 ).
  • client events include among others, entering text in a screen field, moving the mouse over text or a screen button, clicking the mouse, highlighting a button in the screen, drag & drop, a window is hidden, and new data is available.
  • FIG. 11 depicts how the system handles the client events ( 900 ).
  • the CRE checks if there is a listener listening to this event ( 904 ). If there is no listener listening to this event ( 907 ) the CRE waits for a new client event ( 910 ).
  • the CRE determines if the listener is a business logic component in the client side or a server-side event handler ( 906 ). If the listener is a client-side business logic component ( 911 ), the CRE checks if this client-side business logic component is instantiated, i.e., the business logic component has been created and initialized in the memory ( 912 ). If the client-side business component is not instantiated ( 915 ) the CRE loads it from the cache and instantiates it ( 922 ). If the client-side business component is instantiated the CRE locates the instantiated instance ( 924 ), and invokes the registered listener method for handling this event ( 926 ).
  • the CRE processes the event according to the client-side business component listener method and produces a result ( 928 ).
  • the CRE checks if the result is a markup document or a direct client DOM manipulation through an API ( 930 ). If the result is a markup document 933 the CRE processes the markup document ( 918 ) and displays the result ( 920 ). If the result is a direct client DOM manipulation through the API ( 931 ) the CRE executes the API calls ( 932 ) and displays the result ( 920 ).
  • DOM modifications result in changes in the application state which may be changes entered through the user interface or internal data changes. The system then waits for a new client event ( 910 ).
  • a client-side listening component may be a client side business logic component, macro statements defined in markup documents, and local URL invocations, among others.
  • a server-side event handler may be a JavaTM server page, a web service call, a servlet, and an Active Server Page, among others.
  • the application state is maintained in an XML Document Object Model (DOM). This DOM is maintained on the client side by the CRE and by the server. When the user interacts with the application, the CRE updates the client side DOM accordingly to reflect the user's inputs.
  • the application's server-side business logic dictates a change in the state of the application, for example, making a Window invisible, the server automatically updates the server side DOM.
  • either the client side or the server side DOM is updated, either the CRE or the server send a message to the corresponding party to synchronize its DOM, respectively.
  • the application is still available because business logic code and markup documents have been cached on the client side, and the application state is available on the client side as well. Changes of the application state are maintained in the DOM.
  • the client runtime and server runtime automatically synchronize the DOM.
  • the server may package a group of modules together, or all modules together into one deployment module and downloads this deployment module to the client machine.
  • This is particularly useful for the purpose of offline computing where all required offline computing functionality and data can be packaged into one deployment module and downloaded to the client machine at once. After such downloading, the deployment module can run on the client machine without any connectivity until further modules or data are required.

Abstract

A network-based computing system that automates, simplifies, and optimizes the compilation, deployment, and execution of an application by any type of a client machine connected to a server via any type of a network connection. The system includes a client runtime environment, a server runtime environment and an object-oriented markup-business logic binding mechanism. The client runtime environment manages client side code and screen definitions. The server runtime environment dynamical compiles code to ensure client platform compatibility. The system delivers network applications on demand, by separating them into lightweight modules and delivering these modules.

Description

    CROSS REFERENCE TO RELATED CO-PENDING APPLICATIONS
  • This application is a continuation of U.S. application Ser. No. 10/754,782 filed on Jan. 9, 2004 and entitled “System and Method for Network-Based Computing” which is commonly assigned and the contents of which are expressly incorporated herein by reference.
  • FIELD OF THE INVENTION
  • The present invention relates to a system and a method for network-based computing, and more particularly, to network-based computing that provides network applications that can be automatically deployed, compiled, and executed by any type of a client machine connected to a server via any type of a network connection.
  • BACKGROUND OF THE INVENTION
  • A typical computing system includes hardware and software components. Hardware components include computing devices such as personal computers (PC), mainframe computers, and computing circuits, among others. The basic architecture of a computing device includes a central processing unit (CPU), which executes instructions, and a memory unit, which stores instructions and data. Instructions and data are transmitted from the memory unit to the CPU and the results of the CPU operations are sent back to the memory unit. Software components are application programs, which contain the set of instructions that are executed by the CPU unit. Application programs include among others, system programming software, drawing software, word processing software, spreadsheet evaluation software, enterprise resource management software, customer relationship management software, data analysis software, customer self-help software, network and storage management software, mathematical and scientific software. A computer programmer develops an application program by first coding a set of instructions in a source file using the grammar rules of a programming language. In the example of FIG. 1, a programmer writes a source file using the grammar and syntax of the Java™ programming language 82. Next, the Java™ source file passes through a Java™ compiler 84 where it gets analyzed and parsed. The parsed file is then used to generate a Java™ bytecode 86, i.e., a code that is understood by a Java™ Virtual Machine (JVM™). The compiled Java™ bytecode file 86 is then stored in the memory of the computing device. When a user wants to run the particular application program the computing device retrieves the compiled Java™ bytecode file 86 from the memory, the Java™ Virtual Machine 88 executes it, and the computing results are displayed 89. The compiled Java™ bytecode file 86 may also be stored in a computer readable storage medium such as a compact disk (CD) or a magnetic floppy disk or tape. These computer readable storage media may also be used to distribute and install the application program, i.e., the compiled Java™ bytecode files, in other computing devices. This computing system is sufficient for independent computing devices.
  • A network-based computing system includes a central server and a plurality of computing devices, i.e., client machines, that are connected with each and to the server via a network. Application programs are stored in the central server and can be deployed to the client machines via the network. Alternatively, application programs can be installed in the client machines via a manual distribution of computer readable media such as CD or floppy disks containing the compiled application code. Network-based computing is used for large enterprises that have multiple computing devices in multiple locations that interact with each other and with the server via a network connection. An application program in the network-based computing system includes a server program that is stored in the server and a client program that is stored in the memory of a client machine. The server program runs on the server and the client program runs on one of the client machines. Large enterprises utilize network-based computing to run enterprise application such as SAP's Enterprise Resource Planning software and custom internal applications. For example, a financial services company may utilize an internal Investment Portfolio Management application to perform stock analysis. When a portfolio manager wants to do a specific stock analysis, he starts the client program for the Investment Portfolio Management application in the client machine. The client machine loads the multi-megabyte client program, and then receives and processes the portfolio manager's requests. The client machine may also send further requests to the server program via the network to gather any necessary data. Next, the client program receives the necessary data, analyzes the data and presents the result in an appropriate format to the portfolio manager.
  • Processes associated with network-based computing include application development, application deployment, and application execution, among others. Application development refers to the coding, compiling, and debugging of the server and client programs that can be run by the server and the various configurations and operating systems of the client machines, respectively. Application deployment refers to the distribution and installation of the various client programs in the various client machines. Application execution refers to the execution of the compiled server and client programs by the server and the various client machines of the network, respectively.
  • The main issues with the application development for a network-based computing system involve around client platform and device configuration incompatibilities. Client platform incompatibilities include different operating systems and different hardware. The operating systems may be various versions of Windows, Mainframe, Macintosh, Unix, Linux, and Palm™. The different hardware may be Pocket PCs, desktops, laptops, workstation, phone systems, personal digital assistants (PDA) and smart television sets. Device configuration includes the specific settings that a given application may require, such as the Dynamic Link Library (DLL) version and registry for typical Windows applications. For companies with thousands of users and client machines, client platform and device configuration incompatibilities result in a significant amount of complexity and increased costs for the development of network applications.
  • The main issues with the application deployment in a network-based system involve around the distribution of the client program to thousands or even hundreds of thousands of client machines and the confirmation that each client machine always contains the most appropriate version of the application. The following approaches are the most commonly used today for handling code distribution and configuration:
  • a) CD/Floppy disk distribution and manual installation and configuration: Information System (IS) personnel install the compiled client program from a CD or floppy disks directly onto the client computer and manually configure the application for each client computer. This manual process is repeated every time the code is upgraded. Considering that an enterprise can have thousands of desktop computers distributed in many different offices, this approach is very inefficient, time consuming and costly.
  • b) Manual network download, installation and configuration: This approach enables an end user to download and install the client program into his computer over a Local Area Network (LAN), a Wide Area Network (WAN) or the Internet. However, considering that the client program can be easily tens of mega bytes, downloading such a big file and configuring the application can take each user up to several hours to achieve. Considering an enterprise that has thousands of users, the amount of productivity loss due to this manual downloading process can be significant. Furthermore, in cases where the network connection is slow and has limited bandwidth (i.e., dialup or wireless connection), this is simply not a viable option.
  • The issue with the client program execution is that the current program execution model requires loading almost the entire program into memory before the user is able to run the application. As was mentioned above, client programs are typically multi-megabyte files and loading such big files into memory creates lengthy delays for users. Further, this execution model creates increasing demands on hardware because it requires faster CPU, bigger memory, more storage, and a faster network, all of which translate into costs and performance issues.
  • Alternative approaches to this static network-based computing system include the Java™ Applet approach and the Hyper Text Markup Language (HTML) web page approach. In the Java™ Applet approach the client component of a network application is written as a Java™ Applet, and the end users can access this application without the need to install it in advance. However, Java™ Applets have severe technical limitations that restrict its practical use to simple application only. For complex enterprise applications, the Java™ Applet not only performs poorly but also can easily have a footprint in excess of 1 MB, which requires lengthy downloading which in turn effectively prevents users from using it over the Internet or WAN. In addition, Java™ Applets require a Java™ Virtual Machine (JVM™) on the client machine. The JVM™ incompatibilities and lack of JVM™ on some machines both add to the failure of wide adoption of Java™ Applets for enterprise applications.
  • In the HTML web page approach companies use HTML for publishing simple application screens. In this approach, the entire application is running on the server. Each screen is formatted into an HTML web page and displayed in a web browser. Some simple client-side logic can be added to the HTML page using technologies, such as JavaScript™. However, this approach is limited to applications that require minimal user interactivity and functionality. Network applications using this approach sacrifice many of the features and functionality associated with client-side computing, such as offline computing, drag&drop, multiple windows, spreadsheet behavior, among others. The “click and refresh” user interaction model associated with web browsing is not suitable for network applications because this model not only consumes significant bandwidth by sending and re-sending redundant information, but it also significantly lowers user productivity by keeping users waiting with every mouse click. In this scenario, the client-side business logic is also limited because a scripting language, such as JavaScript™, does not scale well to a large team of developers, unlike the more robust Object-oriented programming (OOP) languages like Java™ and C++. As a result, HTML is used only for simple applications. Important applications are still being written as traditional Client/Server applications using OOP languages.
  • In summary, the current approaches for network-based computing are costly, inefficient and complicated for developers. In order to use an application, users have to go through a lengthy downloading, configuration and loading process. Whenever a new version of the application is available, users have to go through the same process again. Platform incompatibilities often prevent many users from being able to run the application at all. Companies often have to maintain a significant technical support team to manage and deal with application configuration and management. Desktops need to be constantly upgraded to keep up demands from bigger and bigger client programs. For users that are distributed over a wide area network (WAN) or even the general public Internet, where bandwidth is very limited, the current approaches are simply not viable options. Though there are alternative approaches, like HTML, which can significantly lower the client footprint and reduce the client incompatibility problem, such approaches are not able to deliver the functionality and performance required for most business applications.
  • Accordingly, there is a need for a network-based computing system that automates, simplifies, and optimizes the compilation, deployment, and execution of an application by any type of a client machine connected to a server via any type of a network connection.
  • SUMMARY OF THE INVENTION
  • In general, in one aspect, the invention features a computer application program including at least one markup document, at least one business logic component associated with and applied directly to the at least one markup document and an object oriented binding mechanism binding the at least one markup document to the at least business logic component and the reverse.
  • Implementations of this aspect of the invention may include one or more of the following features. A client runtime environment (CRE) may receive and convert the at least one markup document into an object-oriented representation. The object-oriented representation may include one or more markup objects, one or more user interfaces, and one or more data sets. The at least one business logic component may include one or more methods used as event handlers for a markup object event. The object oriented binding mechanism may include invoking the one or more methods by the one or more markup objects by firing a markup object event. The object oriented binding mechanism may further include accessing and modifying the one or more markup objects by the at least one business logic component via an Application Program Interface (API). The API may be a markup object API or a Document Object Model (DOM) API. The one or more markup objects may include a parent markup object and a child markup object and the child markup object may have one or more markup object properties inherited from the parent markup object. The one or more markup object properties may be a user interface definition, a data set definition or an event handler definition. The parent markup object may have one or more user interface definitions, one or more data definitions and one or more event handlers and the child markup object may inherit the one or more user interface definitions, the one or more data definitions and the one or more event handlers from the parent markup object. The one or more markup objects may include a parent markup object and a child markup object and the child markup object may overwrite one or more markup object properties of the parent markup object and replace them with one or more markup object properties of the child markup object. The at least one markup document may be written in a markup language including among others, XML, XUL, SVG, Xforms, XAML, HTML, HTML related languages, text, or combinations thereof. The one or more business logic components may be written in a programming language including among others, Java™, JavaScript™, J#, C#, C+, C++, Visual Basic, ActionScript, XSL, XQuery, or XPath.
  • In general, in another aspect, the invention features a network application program having one or more modules wherein each module includes at least one markup document, at least one business logic associate with the at least one markup document and an object oriented binding mechanism binding the at least one markup document to the at least business logic component and the reverse.
  • In general, in another aspect, the invention features a method of binding a markup document with one or more business logic objects including coding the markup document using a markup language, coding the one or more business logic objects using an object oriented programming language and associating the markup document with the one or more business logic objects. Next, constructing an object oriented representation of the markup document thereby generating one or more markup objects. Next, firing one or more markup object events by the object oriented representation thereby invoking the one or more business logic objects for processing the events and finally manipulating the markup objects by the one or more business logic objects. The business logic objects may manipulate the markup objects via a markup object API or a Document Object Model (DOM) API.
  • Among the advantages of this invention may be one or more of the following. The computing system enables partitioned delivery and execution of a network application from a central server to any client machine connected to the server via a network connection. The network connection may be a low bandwidth network. The client machines may include any type of computing platforms and devices. The network application includes markup documents, business logic components and an object-oriented binding mechanism binding the markup documents to the business logic components and the reverse. The markup documents may be scripted using any type of a markup language including among others, XML, XUL, SVG, Xforms, XML related languages, HTML, HTML related languages, text, and combinations thereof. The business logic components may include source code scripted in any programming language including among others, Java™, JavaScript™, J#, C#, C+, C++, Visual Basic, ActionScript, XSL, XQuery, and XPath. A compiler system converts the source code to any type of executable bytecode. This compiler system configuration provides flexibility in both the programming side of the application and the execution side of the application.
  • The details of one or more embodiments of the invention are set forth in the accompanying drawings and description below. Other features, objects and advantages of the invention will be apparent from the following description of the preferred embodiments, the drawings and from the claims.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • FIG. 1 is a block diagram of a prior art process for writing, compiling and executing of an application;
  • FIG. 2 is an example of a network-based computing system;
  • FIG. 3 is a block diagram of the software and hardware components of a simple network-based computing system;
  • FIG. 4 is a schematic diagram of the server compiler of the application server of FIG. 3;
  • FIG. 4A is a detailed block diagram of the universal Java™ bytecode compiler of FIG. 4;
  • FIG. 4B is a detailed block diagram of the universal XML compiler of FIG. 4;
  • FIG. 5 is a block diagram of an object-oriented application according to this invention;
  • FIG. 6 is a schematic diagram of the markup-business logic binding mechanism of this invention;
  • FIG. 7A-FIG. 7B are code examples of the markup-business logic binding mechanism;
  • FIG. 7C is a screen shot of the example of FIG. 7A;
  • FIG. 7D is another screen shot of the example of FIG. 7A;
  • FIG. 8 is a schematic diagram of the object-oriented markup object declaration and instantiation;
  • FIG. 9 is a schematic diagram of the module structure of a network-based application according to this invention;
  • FIG. 10 is a flow diagram of the process of deploying, compiling and executing a network-based application according to this invention; and
  • FIG. 11 is a flow diagram of the event handing process of this invention.
  • DETAILED DESCRIPTION OF THE INVENTION
  • Referring to FIG. 2, a network-based computing system 70 includes a server 72 and client machines 73, 74, 75, and 76. The client machines include a personal computer 73, a laptop computer 74, other computing devices 75, and a wireless communication device 76. Client machines 73, 74 and 75 are connected to the server 72 via a network connection 78. Client machine 76 is connected to the server 72 via a wireless network connection 79. There may be several additional client machines including personal computers, laptop computers, Linux machines, workstations, computing circuits, and wired communications devices, such as telephone and television. Network connection 78 may be the Internet, the World Wide Web (WWW), a Wide Area Network (WAN), a Local Area Network (LAN), a Personal Area Network (PAN) or a telecommunication network. The wireless communication device 76 may be a mobile phone, a personal digital assistant (PDA), a pager, a wireless laptop computer, a personal computer, a television, and programmable versions thereof or combinations thereof. The wireless network 79 may be a wireless wide area network (WWAN), a wireless local area network (WLAN), a wireless personal area network (WPAN) or a private communication network.
  • Referring to FIG. 3, a block diagram of the software and hardware components of a simple network computing system 200 includes an application server 210, a client machine 220, and a web server 219. The application server 210 runs behind the web server 219, and runs server-side application code (or server-side business logic) 212. The web server 219 delivers markup documents or electronic messages generated by the server side application code 212 to a client web browser 230 residing inside the client machine 220. Electronic messages are communication messages delivered electronically for information exchange. Markup documents are electronic documents, i.e., files, written using a markup language such as XML or HTML. A markup language is a conventional language for describing the contents of an electronic document that is to be viewed or printed on a computer output device such as a computer monitor. A markup language document can contain text, images, JavaScript™, and hyperlinks, among others. A real time, bidirectional, reliable messaging system 240 transmits messages between the client web browser 230 and the web server 219 over an HTTP web connection. The application server includes in addition to the server side application code 212 a Server Runtime Environment (SRE) 214. The SRE 214 runs behind the HTTP web server 219 and inside the application server 210. The SRE 214 includes a server compiler 216, a server cache 218, a communications module 215, and other functional modules 217. The functional modules 217 include an Application Server Interface, an XML Parser, Clustering, Storage, and an Execution Engine. The application server interface module enables the SRE 214 to run inside the application server 210 and enables applications inside the application server 210 to access the SRE's functionalities. The XML Parser module is responsible for parsing XML documents that come from the various client machines or other information sources such as other backend connections. The parsing results may be stored in the Storage module. The clustering module provides support for clustering the SRE and the execution engine module executes the compiled server-side application code 212.
  • The client machine 220 includes a client runtime environment (CRE) 224 that runs outside the client web browser 230 and client-side application code 222 (or client-side business logic). In other embodiments the CRE runs inside the client web browser 230. The client side application code 222 includes Extensible Markup Language (XML) documents and procedural code. The client machine 220 is protected by a client side firewall 244 and the web server 219 is protected by a server side firewall 242. The CRE 224 processes markup documents and executes the client-side application code 222. The CRE 224 includes a client cache 226, a communication module 225, a state synchronization and persistency module 228 and other functional modules 227 such as an XML parser, a user interface, storage, security, and an execution engine. The XML Parser is responsible for parsing XML documents that come from the application server 210. The parsing results may be stored in the client cache 226 as part of the application's client side state. The user interface module is responsible for displaying the user interface and interacting with the user according to the application's XML description. The execution engine module is capable of running client side application code 222. The client cache 226 maintains the application's client side state and is updated by the CRE automatically. The synchronization and persistency module 228 is responsible for synchronizing the client cache 226 with the application server 210, and saving and/or retrieving the client cache 226 from persistent storage.
  • The CRE 224 is centrally managed by the SRE 214. The CRE 224 is automatically downloaded from the application server 210 and installed in the client machine 220 the first time a user access a client application. After the initial installation, the SRE 214 automatically manages the versioning and updating of the CRE 224. Different CREs 224 are used for the different client platforms. For example, different CREs are used for a Java™ Virtual Machine, a NET CLR, or a Flash Player. The executable application code formats of these three client platforms are: Java™ bytecode, .NET CLR bytecode and Flash bytecode, respectively. The application code 222 is delivered in three different executable code formats for these three client platforms, accordingly.
  • Referring to FIG. 4, the server compiler 216 is a software program that translates source code written in any supported programming language into executable code of any supported executable format. As shown in FIG. 4, the source code is written in a programming language, such as Java™, C#, JavaScript™, and XML, among others. The supported executable formats are Java™ bytecode, .NET CLR bytecode, or Flash bytecode, among others, depending on the client platform. For example, when the client platform is running a Java™ Virtual Machine 360, all input source files, no matter which language they are being written in, are compiled into Java™ bytecode executable files by the server compiler 216. Similarly, if the client platform is running a .NET CLR, all source code files are compiled into .NET CLR bytecode.
  • The server compiler 216 includes a plurality of specific universal compilers including among others, a universal Java™ Bytecode compiler 312, a universal .NET CLR (Common Language Runtime) compiler 314, a universal JavaScript™ compiler 316, a universal Flash SWF compiler 318, and a universal XML compiler 320. The server compiler 216 also includes a server compiler control logic 310 that detects the type of the client platform, invokes compiling and caching of a client platform appropriate executable code and delivers the appropriate executable code to the corresponding client platform. When the server compiler 216 receives a request from a certain client machine, the control logic 310 first characterizes the client machine to see which executable format is supported by this client machine. If a compiled executable code of the supported format is available in the server cache 218 and the source file has not changed since last compilation, the server compiler control logic 310 sends the cached executable code to the client machine directly. If the source file has been changed since the last compilation, the control logic 310 prompts the server compiler 216 to retrieve the source file, compile the source file into the appropriate executable code, cache the executable code in the server cache 218 and send the executable code to the client machine.
  • Each universal compiler receives an input file written in any programming language, such as Java™, C#, JavaScript™, C+, C++, Visual Basic, and delivers an output file in one executable format specific to a certain client platform. The input files 302, 304, 306 and the output files 332, 334, 336, 340 may also include markup documents written in XML.
  • Referring to the example of FIG. 4A, the universal Java™ bytecode compiler 312 receives source code files written in programming languages such as Java™ 302, C# 304, JavaScript™ 306, among others, and delivers a Java™ Virtual Machine executable Java™ bytecode file 332. The universal Java™ bytecode compiler 312 includes a plurality of custom developed language compilers, such as JavaScript™ compiler 353, a plurality of commercially available language specific compilers, such as Java™ compiler 351, J# compiler 352, C# compiler, among others, and a control logic 355. Java™ compiler 351 is commercially available from Sun Microsystems of Santa Clara, Calif., J# compiler 352 is commercially available from Microsoft of Redmond Wash. The JavaScript™ compiler 353 is custom developed by Nexaweb and compiles JavaScript™ files into Java™ bytecode. Similarly, the universal .NET CLR compiler 314, the universal JavaScript™ compiler 316, and the universal Flash SWF compiler 318, receive input files written in any programming language and deliver bytecode files executable by a .NET CLR engine, a JavaScript™ engine, and a Flash player, respectively. The control logic 355 module includes rules for handling the various programming language codes and processes the input files. When an input file is received, control logic module 355 checks which language the source code file is being written in and selects the appropriate language specific compiler to compile the source code file into executable code in the desired executable format. For example, control logic 355 of the Universal Java™ bytecode compiler 312 would select the JavaScript™ compiler 353 to compile JavaScript™ source files and Java™ compiler 351 to compile Java™ source files.
  • Referring to FIG. 4B, the universal XML compiler 320 receives files written using various markup languages such as, XHTML™ (362), x-Forms (364), HTML (365), XAML (370), SVG (368), and delivers XML code (340) executable by an XML execution engine (366). The universal XML compiler 320 includes a plurality of markup language specific compilers, such as XHTML™ compiler 371, XAML compiler 372, SVG compiler 373, among others, and a control logic 355. The control logic 355 is responsible for selecting and invoking a markup language specific compiler to compile a source file written in the specific markup language. The language specific compiler takes the markup document and converts it into a new markup document in the executable format required by the execution engine. For example, if the execution engine is a SVG rendering engine that knows how to render SVG and the source code file is written using XAML, the XAML compiler takes the XAML input and converts it into SVG format. This compilation process can be achieved using an XML Stylesheet Transformation (XSLT), or some other lexical analysis and transformation.
  • The compiled bytecode files 332, 334, 336, 340 may be stored in the server cache 218, shown in FIG. 4. When the CRE 224 of a client machine 220 requests a specific file, the SRE 214 determines the particular executable format of the CRE 224 and checks if this particular format has already been compiled and is stored in the server cache 218. If the particular compiled bytecode exist in the server cache 218 and the code has not been modified since the last time it was compiled the SRE 214 downloads the executable file to the CRE 220 an stores it in the client cache 226. Otherwise, the SRE 214 will invoke the server compiler 216, and first compile the requested code in the particular executable format and then download it to the CRE 224 and store it in the client cache 226.
  • This invention utilizes object-oriented programming methodology to develop object-oriented application programs. Object-oriented application programs typically model a problem using an “object model” that defines classes of objects representing elements of the problem. A class of objects is defined in terms of the relationship of the class to other classes, the data and properties (or attributes) associated with objects in the class, and the operations (or tasks) that can be performed on objects in the class. During execution of an object-oriented application program, instances of the classes in the object model, referred to as “objects,” are produced and manipulated. Computation on these “objects” is performed by calling on “methods” defined in business logic components associated with these “objects”. For example, in an accounting management program, the various accounts are defined as the program objects. Each object, i.e., account, has attributes including account name, account number, amount deposited in the account, among others. Tasks associated with these account objects may be “get account number”, “set account name”, “set account amount”, among others. Objects interact with each other and with the business logic code via events or messages. An object may fire an event (or send a message) in order to modify its own properties, or state. Events are received and processed by the subprograms or business logic components associated with these objects. Object-oriented programming languages are well known in the art and are described in “Programming languages” Chapter 11, p 435-483, edited by Robert W. Sebesta.
  • Referring to FIG. 5, the object-oriented application code 400 includes one or more markup documents 402 and one or more business logic components 406. The markup documents 402 are files written using an XML markup language. The business logic components 406 include instructions for performing tasks upon the program objects. These instructions are formulated as source code files written in a programming language, such as Java™, JavaScript™, C#, Visual Basic (VB), J#, among others. The business logic components 406 are also program objects. The Client Runtime Environment (CRE) 224 receives the markup documents 402 and converts them into object-oriented representations, i.e., markup objects 404. The markup objects 404 may be user interfaces (UI) 401 or data 403. Each markup object 404 may have events associated with it. For example, in the case of a UI markup object that has input fields or buttons, an event may include highlighting the button or input field, entering text in the field, or clicking the button, among others. The event is received and processed by the business logic component, so that the state of the object is modified. In the example of the user interface with the input fields, where text is entered in the input fields, the business logic component modifies the UI to display the entered text. The object oriented representations of the markup documents 405 and business logic components 406 are bound via a markup-business logic binding mechanism 500.
  • Referring to FIG. 6, the markup-business logic binding 500 includes the process of binding the markup objects to the business logic components (520) and the process of binding the business logic components to the markup objects (530). In the markup object to business logic component binding 520, markup objects 510 defined in markup document 550 invoke business logic components 540 by firing markup object events 521. The business logic components 540, include definitions of methods that are used as the event handlers for the markup object events. Upon firing of an event, the CRE invokes the associated method in the corresponding business logic component, passes necessary information about the event to the method and executes the method. In the previous example of the user interface markup object that has several input fields, firing an event may be entering a user's phone number in the appropriate input field. The business logic component receives this markup object event, validates it and formats the phone number for display.
  • In the business component to markup objects binding 530, business logic components 540 can access and modify the markup objects 510 via a markup object Application Program Interface (API), or a Document Object Model (DOM) API, 531. In one embodiment, the CRE 224 parses and stores the markup document 550 into a DOM, and exposes this DOM as a set of API that can be invoked by business logic components 540. Business logic components 540 invoke this DOM API to programmatically manipulate the markup document 550 stored in the DOM. This feedback mechanism via the markup object API 531 may be “a form validation” process or an internal calculation that will result in modifying the markup objects 510. In an example of a “form validation” process the user enters in the UI a phone number that has three digits. The business logic component recognizes that a three digit phone number is not valid, rejects the input, displays an error in the UI and requests a valid phone number.
  • This two-way binding mechanism 500 enables the clear separation of business logic, presentation and data. The HTML and JavaScript™ interaction models in web browsers share a similar architecture. However, the present invention differs from these prior art models because it allows for object-oriented binding. The markup documents are converted into object oriented representations (markup objects) and the business logic components become program objects as well. The object-oriented binding is then a binding between these objects, i.e., the markup objects and the program objects. In the prior art example, the business logic is written as scripts, which are not object oriented, and the binding is a binding between program methods to HTML objects. This object-oriented binding of this invention allows for the development of complex applications and provides programming language and execution format independence. In other words, the business logic code may be written in any programming language including Java™, JavaScript™, C#, J#, VB, and C+, and the markup documents may be written in any markup language including XML, text, and HTML, among others. If the programming language is not object oriented, the source code can be compiled by the universal compiler into an object oriented executable code. Several XML specifications may be used including XUL (XML User Interface Language), SVG (Scalable Vector Graphics) and XForms. The combination of these XML languages creates a rich environment that supports all functionalities of all network applications including typical Windows graphical user interface, forms, 2D graphics and animation.
  • A code example 600 of the markup-business logic binding mechanism 500 is shown in FIG. 7A and FIG. 7B. A markup document 610 is written using XML. The markup document 610 defines a client-side logic object “bean1621, a parent button “parentBtn” 632, a child button “childBtn” 635, and a data object “companyInfo” 641. The client-side logic object “bean1621 defines a client-side programming object whose source code is “com.nexaweb.clientbean.DemoBean”, effectively associating the business logic component 650 with this markup document 610. The source code for business logic component 650 is written using the Java™ programming language and defines a Java™ class with three different methods, including “init” 660, “doClick” 670, and “doOver” 680. The markup document to business logic binding 520 is achieved by using the three methods 660, 670, 680 of the business logic component 650 as the event handlers for events fired by the three markup objects 621, 632, and 635, respectively. Method 660 processes the “onload” event for markup object 621, method 670 processes the “oncommand” event for the parent button 633, and method 680 processes the “onmouseover” event for the child button 635. Whenever such an event happens, the CRE invokes the corresponding method in the business logic component to process it. An example of the business logic to markup binding 530 is shown in the implementation of the three methods 660, 670, 680 in the business logic component 650. For example, using the DOM API exposed by the CRE, the “doClick” method 670 inspects the event information, retrieves the event source, which should be the markup object that the user clicked, and sets the “text” attribute of this markup object to be the processed result. For example by clicking on the parent button object 632 the text “You clicked button: parentBtn” appears on the UI screen 633, as shown in FIG. 7C. Similarly, by clicking on the child button object 635 the text “You clicked button: childBtn” appears on the UI screen 636, as shown in FIG. 7D.
  • FIG. 8 shows how this invention allows object-oriented markup object inheritance. This process greatly simplifies the creation and management of markup documents and increases the flexibility of markup documents. The parent markup object 710 includes a user interface definition 720, an object specific data definition 730 and object behavior (or event handler) definition 740. The child markup object 750 includes a user interface definition 760, an object specific data definition 770 and object behavior (or event handler) definition 780. The child markup object 750 inherits all these UI, data and behavior definitions 760,770 and 780, respectively, from the parent markup object 710. The child markup object 750 can also optionally overwrite the corresponding parent definitions and add new definitions. This object-oriented approach allows for inheriting and changing not only object attributes, but also allows for entire different object behavior by replacing the parent object's event handler definition with child specific event handlers. Referring back to the code example of FIG. 7A, the “childBtn” 635 inherits all definitions (UI, data and behavior) from the “parentBtn” 632. However, markup object specific data are changed, i.e., the “id” is changed from “parentBtn” to “childBtn”. Similarly the user interface definition is changed, i.e., the value of “text” attribute is changed so that the text “You clicked button: childBtn” is displayed instead of “You clicked button: parentBtn”. The “childBtn” inherits the object behavior from “parentBtn” so that the “oncommand” event will invoke the “bean1.doClick ( )” method 670 for the child markup object, as well. The child markup object 750 also modifies the behavior definition of the parent markup object 710 by binding the “bean1.doOver ( )” method 680 to the “onmouseover” event so that the “onmouseover” event will invoke the “bean1.doOver ( )” method 680 for the parent markup object, as well.
  • Application programs are typically multi-megabyte files. Loading such big files into memory creates lengthy delays for users and places great demands on the hardware components because it requires faster CPU, bigger memory, more storage, and a faster network, all of which translate into costs and performance issues. The present invention solves these problems by separating the application code into small independent modules each of which can be downloaded and executed independently. Referring to FIG. 9, application code 400 includes N number of modules, Module 1 (410), Module 2 (450), Module 3 (480), . . . Module N (not shown). Each module includes one or more markup documents and optionally one or more business logic components. In the example of FIG. 9, Module 1 (410) includes a markup document 420 and business logic components A (430) and B (440). Markup document 420 defines two markup objects, i.e., a User Interface (UI) 422 and a Data file 424. Module 2 (450) includes a business logic component C (470) and a markup document 460 defining a User Interface 462 and a Data file 464. Module 3 (480) includes business logic component A (430), business logic component E (494) and a markup document 490 defining a User Interface 492 and a Data file 493. Different modules may share business logic components. For example, Module 3 (480) uses the same business logic component A (430) as Module 1(410). In this case the system 200 of FIG. 3 uses client-side caching 226, as well as server-side caching 216 to avoid loading the same module or component more than once. Accordingly, although the entire application code 400 is composed of many XML documents and many business logic components, each module may require only one XML document and a few compiled business logic components, therefore resulting in a small footprint for each module. This small footprint of each module enables fast application code downloading. Furthermore, once a module is downloaded in the client machine it is stored in the client caching and it can be reused in the future without requiring a new download. The server also provides for automated updating of the modules that were previously downloaded in the client machine and were stored in the client cache.
  • Referring to FIG. 10, the process 800 of running and application through a client machine includes the following steps. When a user wants to use a network application he starts the CRE and enters a request to start the client program (802). The CRE receives the request (804) and checks to see if the initial module is available in the local client cache (806). If the module is not available in the local cache (807), the CRE sends a request to the server (SRE) to download the specific module (808). The server delivers the markup document that describes the specific module to the CRE (810) and the CRE inquires if this markup document needs to be cached (812) by checking the document properties or configuration information. If this markup document needs to be cached (813), the CRE caches it in the local client cache (814) and then proceeds to the next question (815). Similarly, if the markup document does not need to be cached in the local client cache (811), the CRE proceeds to the next question (815). If the module is available in the local cache (809), the CRE skips the downloading process and proceeds to the next question (815), as well. Next, the CRE checks the module properties or configuration information to see if this module requires a business logic component (816). If no business logic component is required (815) the CRE displays the module to the user (818) and then waits for a user input (820). If the module requires a business logic component (817), process (840) takes place. In process (840), the CRE proceeds to check if the business logic component is available in the local cache (824). If the business logic component is available in the local cache (821), it gets loaded from the local cache (826) in the active memory. If the business logic component is not locally available (823), the CRE sends a request to the server to download the business logic component (828). The server checks if this business logic component has been compiled before for this particular client machine executable format (830), and if it has (831) it downloads the executable code from the server cache to the client cache (834). Next, the CRE stores the executable code in the client machine cache (836) and loads it in the active memory (826). If the business logic component has not been previously compiled for the specific client machine executable format (829), the server first compiles it into an executable code executable by the specific client machine execution engine and stores it in the server cache (832). Next, the server downloads the executable code from the server cache to the client cache (834), where the CRE caches it in the client cache (836) and then loads it in the active memory (826). Finally, both the markup document and the business logic component (837) are present in the active memory and wait for an input from the user (820). If there are more than one business logic components associated with a specific module the process (840) is repeated for each individual business logic component (841). The process 800 is repeated for downloading the next module and the business logic components that are associated with it. Once the CRE receives the markup language document, it immediately processes the document, executes the associated business logic and displays the result to the user. This module-type downloading and execution of a network application has the advantages of being fast and requiring low bandwidth. The storing of the previously downloaded modules and associated business logic in the client-side cache and the server cache and the synchronization of the client-side cache with the server cache allows the client machine to execute the network application offline, even in the case when the network connection is not available.
  • Once the appropriate modules are brought in the active memory of the client machine the user interacts directly with the application through client events. Client events include among others, entering text in a screen field, moving the mouse over text or a screen button, clicking the mouse, highlighting a button in the screen, drag & drop, a window is hidden, and new data is available. FIG. 11 depicts how the system handles the client events (900). When a client event happens (902), the CRE checks if there is a listener listening to this event (904). If there is no listener listening to this event (907) the CRE waits for a new client event (910). If there is a listener listening to this event (905), the CRE determines if the listener is a business logic component in the client side or a server-side event handler (906). If the listener is a client-side business logic component (911), the CRE checks if this client-side business logic component is instantiated, i.e., the business logic component has been created and initialized in the memory (912). If the client-side business component is not instantiated (915) the CRE loads it from the cache and instantiates it (922). If the client-side business component is instantiated the CRE locates the instantiated instance (924), and invokes the registered listener method for handling this event (926). The CRE processes the event according to the client-side business component listener method and produces a result (928). Next the CRE checks if the result is a markup document or a direct client DOM manipulation through an API (930). If the result is a markup document 933 the CRE processes the markup document (918) and displays the result (920). If the result is a direct client DOM manipulation through the API (931) the CRE executes the API calls (932) and displays the result (920). DOM modifications result in changes in the application state which may be changes entered through the user interface or internal data changes. The system then waits for a new client event (910). A client-side listening component may be a client side business logic component, macro statements defined in markup documents, and local URL invocations, among others. A server-side event handler may be a Java™ server page, a web service call, a servlet, and an Active Server Page, among others. In one example, the application state is maintained in an XML Document Object Model (DOM). This DOM is maintained on the client side by the CRE and by the server. When the user interacts with the application, the CRE updates the client side DOM accordingly to reflect the user's inputs. When the application's server-side business logic dictates a change in the state of the application, for example, making a Window invisible, the server automatically updates the server side DOM. Whenever either the client side or the server side DOM is updated, either the CRE or the server send a message to the corresponding party to synchronize its DOM, respectively. When the network is disconnected, the application is still available because business logic code and markup documents have been cached on the client side, and the application state is available on the client side as well. Changes of the application state are maintained in the DOM. When the network connection becomes available, the client runtime and server runtime automatically synchronize the DOM.
  • Other embodiments are within the scope of the following claims. For example, instead of downloading one module at a time, the server may package a group of modules together, or all modules together into one deployment module and downloads this deployment module to the client machine. This is particularly useful for the purpose of offline computing where all required offline computing functionality and data can be packaged into one deployment module and downloaded to the client machine at once. After such downloading, the deployment module can run on the client machine without any connectivity until further modules or data are required.
  • Several embodiments of the present invention have been described. Nevertheless, it will be understood that various modifications may be made without departing from the spirit and scope of the invention. Accordingly, other embodiments are within the scope of the following claims.

Claims (28)

1. A computer application program stored in a computer comprising:
at least one markup document;
at least one business logic component associated with and applied directly to said at least one markup document; and
an object oriented binding mechanism binding said at least one markup document to said at least business logic component.
2. The computer application program of claim 1 wherein a client runtime environment (CRE) receives and converts said at least one markup document into an object-oriented representation comprising one or more markup objects, one or more user interfaces, and one or more data sets.
3. The computer application program of claim 2 wherein said at least one business logic component comprises one or more methods used as event handlers for a markup object event.
4. The computer application program of claim 3 wherein said object oriented binding mechanism comprises invoking said one or more methods by said one or more markup objects by firing a markup object event.
5. The computer application program of claim 4 wherein said object oriented binding mechanism further comprises accessing and modifying said one or more markup objects by said at least one business logic component via an Application Program Interface(API) and wherein said API comprises one of a markup object API or a Document Object Model (DOM) API.
6. The computer application program of claim 5 wherein said one or more markup objects comprise a parent markup object and a child markup object and wherein said child markup object comprises one or more markup object properties inherited from said parent markup object and wherein said one or more markup object properties comprise one of a user interface definition, a data set definition or an event handler definition.
7. The computer application program of claim 6 wherein said parent markup object comprises one or more user interface definitions, one or more data definitions and one or more event handlers and wherein said child markup object inherits said one or more user interface definitions, said one or more data definitions and said one or more event handlers from said parent markup object.
8. The computer application program of claim 7 wherein said one or more markup objects comprise a parent markup object and a child markup object and wherein said child markup object overwrites one or more markup object properties of said parent markup object and replaces them with one or more markup object properties of said child markup object.
9. The computer application program of claim 1 wherein said at least one markup document is written in a markup language comprising one of XML, XUL, SVG, Xforms™, XAML, HTML, XHTML™, HTML related markup languages, text, or combinations thereof.
10. The computer application program of claim 1 wherein said at least one business logic component is written in a programming language comprising one of Java™, JavaScript™, J#, C#, C+, C++, Visual Basic™, ActionScript, XSL, XQuery, or XPath™.
11. A method for developing a computer application program comprising:
providing at least one markup document;
providing at least one business logic component associated with and applied directly to said at least one markup document;
providing an object oriented binding mechanism binding said at least one markup document to said at least business logic component; and
storing said computer application into computer memory.
12. The method of claim 11 further comprising receiving and converting said at least one markup document into an object-oriented representation by a client runtime environment (CRE), wherein said object-oriented representation comprises one or more markup objects, one or more user interfaces, and one or more data sets.
13. The method of claim 12 wherein said at least one business logic component comprises one or more methods used as event handlers for a markup object event.
14. The method of claim 13 wherein said object oriented binding mechanism comprises invoking said one or more methods by said one or more markup objects by firing a markup object event.
15. The method of claim 14 wherein said object oriented binding mechanism further comprises accessing and modifying said one or more markup objects by said at least one business logic component via an Application Program Interface(API), wherein said API comprises one of a markup object API or a Document Object Model (DOM) API.
16. The method of claim 15 wherein said one or more markup objects comprise a parent markup object and a child markup object and wherein said child markup object comprises one or more markup object properties inherited from said parent markup object, and wherein said one or more markup object properties comprise one of a user interface definition, a data set definition or an event handler definition.
17. The method of claim 16 wherein said parent markup object comprises one or more user interface definitions, one or more data definitions and one or more event handlers and wherein said child markup object inherits said one or more user interface definitions, said one or more data definitions and said one or more event handlers from said parent markup object.
18. The method of claim 17 wherein said one or more markup objects comprise a parent markup object and a child markup object and wherein said child markup object overwrites one or more markup object properties of said parent markup object and replaces them with one or more markup object properties of said child markup object.
19. The method of claim 11 wherein said at least one markup document is written in a markup language comprising one of XML, XUL, SVG, Xforms™, XAML, HTML, XHTML™, HTML related languages, text, or combinations thereof.
20. The method of claim 11 wherein said at least one business logic component is written in a programming language comprising one of Java™, JavaScript™, J#, C#, C+, C++, Visual Basic™, ActionScript, XSL, XQuery, or XPath™.
21. A network application program stored in a server memory comprising one or more modules wherein each module comprises at least one markup document, at least one business logic associate with and applied directly to said at least one markup document and an object oriented binding mechanism binding said at least one markup document to said at least business logic component.
22. The network application program of claim 21 wherein said network application program is deployed in a network computing system by first separating said network application into said one or more modules and then downloading separately each of said one or more modules to one or more client machines.
23. The network application program of claim 22 wherein each of said client machines comprises a client runtime environment (CRE) and said CRE further comprises a storage for caching said downloaded one or more modules.
24. The network application program of claim 23 wherein said CRE executes said downloaded one or more modules independently of each other.
25. The network application program of claim 24 wherein said CRE executes said downloaded one or more modules offline.
26. The network application program of claim 25 wherein said server further comprises a compiler system receiving a plurality of input files, and converting any of said plurality of input files into a plurality of output files, respectively, wherein said plurality of input files comprise said network application written in a plurality of different programming languages, respectively, and said plurality of output files comprise a plurality of corresponding executable codes of said network application, respectively.
27. The network application program of claim 26 wherein each of said one or more client machines comprise an execution engine receiving one of said output files and executing said corresponding executable code.
28. The network application program of claim 27 wherein said server is connected to said one or more client machines via a low bandwidth network connection.
US12/209,826 2003-01-10 2008-09-12 System and method for network-based computing Abandoned US20090007160A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US12/209,826 US20090007160A1 (en) 2003-01-10 2008-09-12 System and method for network-based computing

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US43939403P 2003-01-10 2003-01-10
US10/754,782 US7707563B2 (en) 2003-01-10 2004-01-09 System and method for network-based computing
US12/209,826 US20090007160A1 (en) 2003-01-10 2008-09-12 System and method for network-based computing

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US10/754,782 Continuation US7707563B2 (en) 2003-01-10 2004-01-09 System and method for network-based computing

Publications (1)

Publication Number Publication Date
US20090007160A1 true US20090007160A1 (en) 2009-01-01

Family

ID=32718086

Family Applications (2)

Application Number Title Priority Date Filing Date
US10/754,782 Expired - Fee Related US7707563B2 (en) 2003-01-10 2004-01-09 System and method for network-based computing
US12/209,826 Abandoned US20090007160A1 (en) 2003-01-10 2008-09-12 System and method for network-based computing

Family Applications Before (1)

Application Number Title Priority Date Filing Date
US10/754,782 Expired - Fee Related US7707563B2 (en) 2003-01-10 2004-01-09 System and method for network-based computing

Country Status (4)

Country Link
US (2) US7707563B2 (en)
EP (1) EP1588230A4 (en)
JP (1) JP2007524875A (en)
WO (1) WO2004063900A2 (en)

Cited By (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060005114A1 (en) * 2004-06-25 2006-01-05 Richard Williamson Procedurally expressing graphic objects for web pages
US20070005758A1 (en) * 2005-07-01 2007-01-04 Microsoft Corporation Application security in an interactive media environment
US20070006061A1 (en) * 2005-07-01 2007-01-04 Microsoft Corporation Synchronization aspects of interactive multimedia presentation management
US20070005757A1 (en) * 2005-07-01 2007-01-04 Microsoft Corporation Distributing input events to multiple applications in an interactive media environment
US20070002045A1 (en) * 2005-07-01 2007-01-04 Microsoft Corporation Rendering and compositing multiple applications in an interactive media environment
US20100023955A1 (en) * 2008-07-28 2010-01-28 Marcottage Method and system and apparatus for dynamic software environment
US20100251231A1 (en) * 2009-03-25 2010-09-30 Microsoft Corporation Device dependent on-demand compiling and deployment of mobile applications
US20100293499A1 (en) * 2009-05-14 2010-11-18 Microsoft Corporation Rendering to a device desktop of an adaptive input device
US20100299626A1 (en) * 2009-05-20 2010-11-25 Microsoft Corporation Systems and Methods of Providing Rich User Interface and Animation to Auxiliary Display Devices
US20120001921A1 (en) * 2009-01-26 2012-01-05 Escher Marc System and method for creating, managing, sharing and displaying personalized fonts on a client-server architecture
US8656268B2 (en) 2005-07-01 2014-02-18 Microsoft Corporation Queueing events in an interactive media environment
US8799757B2 (en) 2005-07-01 2014-08-05 Microsoft Corporation Synchronization aspects of interactive multimedia presentation management
US20150178254A1 (en) * 2010-09-10 2015-06-25 Facebook, Inc. Efficient Event Delegation In Browser Scripts
US9311284B2 (en) 2002-09-10 2016-04-12 SQGo, LLC Methods and systems for enabling the provisioning and execution of a platform-independent application
US10417036B2 (en) * 2017-02-24 2019-09-17 Oracle International Corporation Evaluation techniques for fast access to structured, semi-structured and unstructured data using a virtual machine that provides support for dynamic code generation
US10817492B2 (en) * 2017-05-05 2020-10-27 Servicenow, Inc. Application extension
US11360976B2 (en) 2017-08-31 2022-06-14 Oracle International Corporation Deployment of javascript and typescript stored procedures and user-defined functions into database management systems

Families Citing this family (115)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6836883B1 (en) * 2000-06-21 2004-12-28 Microsoft Corporation Method and system for compiling multiple languages
JP4662657B2 (en) 2000-07-10 2011-03-30 マイクロソフト コーポレーション Unified data type system and method
US20050038868A1 (en) * 2003-05-19 2005-02-17 Spicer Jeffrey J. Web form host
US7237194B2 (en) * 2003-11-18 2007-06-26 Microsoft Corporation System and method for generating optimized binary representation of an object tree
US20070039007A1 (en) * 2004-05-18 2007-02-15 Spicer Jeffrey J Virtual mind
US7543273B2 (en) * 2004-05-21 2009-06-02 Bea Systems, Inc. Systems and methods for dynamic control of cache and pool sizes using a batch scheduler
US7756910B2 (en) * 2004-05-21 2010-07-13 Bea Systems, Inc. Systems and methods for cache and pool initialization on demand
US20060031760A1 (en) * 2004-08-05 2006-02-09 Microsoft Corporation Adaptive document layout server/client system and process
US20060130051A1 (en) * 2004-12-14 2006-06-15 International Business Machines Corporation Extensible framework for handling submitted form instance data
US8627344B2 (en) * 2004-12-15 2014-01-07 Siebel Systems, Inc. Methods and apparatuses for user interface management
JP2006178912A (en) * 2004-12-24 2006-07-06 Fujitsu Ltd Information processing method and program
US9535679B2 (en) * 2004-12-28 2017-01-03 International Business Machines Corporation Dynamically optimizing applications within a deployment server
US7707547B2 (en) * 2005-03-11 2010-04-27 Aptana, Inc. System and method for creating target byte code
US8271964B2 (en) * 2005-05-16 2012-09-18 Microsoft Corporation Extensible software development services
US20070006065A1 (en) * 2005-07-01 2007-01-04 Microsoft Corporation Conditional event timing for interactive multimedia presentations
US20070006238A1 (en) * 2005-07-01 2007-01-04 Microsoft Corporation Managing application states in an interactive media environment
US20070006062A1 (en) * 2005-07-01 2007-01-04 Microsoft Corporation Synchronization aspects of interactive multimedia presentation management
US20070006079A1 (en) * 2005-07-01 2007-01-04 Microsoft Corporation State-based timing for interactive multimedia presentations
US20070006078A1 (en) * 2005-07-01 2007-01-04 Microsoft Corporation Declaratively responding to state changes in an interactive multimedia environment
TWI263908B (en) * 2005-07-12 2006-10-11 Inventec Corp Update system and method
US20070016592A1 (en) * 2005-07-12 2007-01-18 International Business Machines Corporation Enabling real time decoration for customized topology displays
EP1775661A1 (en) * 2005-10-14 2007-04-18 Research In Motion Limited Displaying using graphics display language and native UI objects
US7966608B2 (en) * 2005-10-26 2011-06-21 Hewlett-Packard Development Company, L.P. Method and apparatus for providing a compiler interface
US8838750B2 (en) * 2005-12-30 2014-09-16 Sap Ag System and method for system information centralization
US20070257715A1 (en) * 2005-12-30 2007-11-08 Semerdzhiev Krasimir P System and method for abstract configuration
US8201189B2 (en) * 2005-12-30 2012-06-12 Sap Ag System and method for filtering components
US8843918B2 (en) * 2005-12-30 2014-09-23 Sap Ag System and method for deployable templates
US20070174420A1 (en) * 2006-01-24 2007-07-26 International Business Machines Corporation Caching of web service requests
US20070240040A1 (en) * 2006-04-05 2007-10-11 Christopher Peters Non-compiled portable algorithm
ATE468556T1 (en) * 2006-04-13 2010-06-15 Microsoft Corp VIRTUAL EXECUTION SYSTEM FOR RESOURCE LIMITED DEVICES
EP1920314A4 (en) * 2006-05-16 2008-09-03 Research In Motion Ltd System and method of skinning the user interface of an application
US7561081B2 (en) * 2006-07-12 2009-07-14 Qualcomm Incorporated Method and apparatus for optimization of SigComp UDVM performance
US7886284B2 (en) * 2006-09-05 2011-02-08 International Business Machines Corporation Using a backend simulator to test and develop xforms templates before linking the xforms templates to backend data processing systems
US8863083B2 (en) * 2006-10-10 2014-10-14 Sap Ag Presenting user interfaces based on messages
GB2444305B (en) * 2007-01-26 2010-12-22 Key Criteria Connect Ltd Method of identifying devices in mobile and desktop environments
GB2445991B (en) * 2007-01-26 2009-04-01 Key Criteria Connect Ltd Method of loading software in mobile and desktop environments
US7761484B2 (en) * 2007-02-09 2010-07-20 Microsoft Corporation Complete mapping between the XML infoset and dynamic language data expressions
US8196092B2 (en) * 2007-06-14 2012-06-05 Verizon Patent And Licensing Inc. XSL dialog modules
US20090063423A1 (en) * 2007-06-19 2009-03-05 Jackson Bruce Kelly User interfaces for service object located in a distributed system
US9727397B2 (en) * 2007-07-23 2017-08-08 Paypal, Inc. Container-less JSP template
US20090172715A1 (en) * 2007-09-28 2009-07-02 Xcerion Ab Network operating system
US8365153B2 (en) * 2007-10-26 2013-01-29 Qualcomm Incorporated Server-based code compilation
US8914774B1 (en) 2007-11-15 2014-12-16 Appcelerator, Inc. System and method for tagging code to determine where the code runs
US8954989B1 (en) 2007-11-19 2015-02-10 Appcelerator, Inc. Flexible, event-driven JavaScript server architecture
US8260845B1 (en) 2007-11-21 2012-09-04 Appcelerator, Inc. System and method for auto-generating JavaScript proxies and meta-proxies
US8566807B1 (en) 2007-11-23 2013-10-22 Appcelerator, Inc. System and method for accessibility of document object model and JavaScript by other platforms
US8719451B1 (en) 2007-11-23 2014-05-06 Appcelerator, Inc. System and method for on-the-fly, post-processing document object model manipulation
US8819539B1 (en) 2007-12-03 2014-08-26 Appcelerator, Inc. On-the-fly rewriting of uniform resource locators in a web-page
US8756579B1 (en) 2007-12-03 2014-06-17 Appcelerator, Inc. Client-side and server-side unified validation
US8806431B1 (en) 2007-12-03 2014-08-12 Appecelerator, Inc. Aspect oriented programming
US8938491B1 (en) 2007-12-04 2015-01-20 Appcelerator, Inc. System and method for secure binding of client calls and server functions
US8527860B1 (en) 2007-12-04 2013-09-03 Appcelerator, Inc. System and method for exposing the dynamic web server-side
US8639743B1 (en) 2007-12-05 2014-01-28 Appcelerator, Inc. System and method for on-the-fly rewriting of JavaScript
US8285813B1 (en) 2007-12-05 2012-10-09 Appcelerator, Inc. System and method for emulating different user agents on a server
US8335982B1 (en) 2007-12-05 2012-12-18 Appcelerator, Inc. System and method for binding a document object model through JavaScript callbacks
US8402435B1 (en) * 2007-12-07 2013-03-19 Adobe Systems Incorporated Systems and methods for organizing source code
US8434076B2 (en) * 2007-12-12 2013-04-30 Oracle International Corporation Efficient compilation and execution of imperative-query languages
US9141377B2 (en) * 2008-02-19 2015-09-22 International Business Machines Corporation Visualization of code units across disparate systems
US8863115B2 (en) * 2008-03-20 2014-10-14 Sap Ag Execution of program code having language-level integration of program models
US8533672B2 (en) * 2008-03-20 2013-09-10 Sap Ag Extending the functionality of a host programming language
US8533673B2 (en) * 2008-03-20 2013-09-10 Sap Ag Language-level integration of programming models
US9454390B2 (en) * 2008-04-04 2016-09-27 Intuit Inc. Executable code generated from common source code
US8291079B1 (en) 2008-06-04 2012-10-16 Appcelerator, Inc. System and method for developing, deploying, managing and monitoring a web application in a single environment
US8880678B1 (en) 2008-06-05 2014-11-04 Appcelerator, Inc. System and method for managing and monitoring a web application using multiple cloud providers
US20090320097A1 (en) * 2008-06-18 2009-12-24 Jackson Bruce Kelly Method for carrying out a distributed search
US8018197B2 (en) * 2008-06-18 2011-09-13 Freescale Semiconductor, Inc. Voltage reference device and methods thereof
US8060603B2 (en) 2008-06-18 2011-11-15 Qualcomm Incorporated Persistent personal messaging in a distributed system
US7596620B1 (en) 2008-11-04 2009-09-29 Aptana, Inc. System and method for developing, deploying, managing and monitoring a web application in a single environment
US9082409B2 (en) * 2008-08-28 2015-07-14 Avaya Inc. Binary-caching for XML documents with embedded executable code
US8539464B2 (en) * 2008-10-30 2013-09-17 International Business Machines Corporation Distributed just-in-time compilation
US8752016B2 (en) * 2008-12-15 2014-06-10 Apple Inc. Converting JavaScript into a device-independent representation
US9354629B2 (en) * 2009-02-19 2016-05-31 Fisher-Rosemount Systems, Inc. Methods and apparatus to configure a process control system using an electronic description language script
US10209968B2 (en) * 2009-05-29 2019-02-19 Adobe Inc. Application compiling
US9117071B2 (en) 2009-06-03 2015-08-25 Apple Inc. Methods and apparatuses for secure compilation
US8677329B2 (en) * 2009-06-03 2014-03-18 Apple Inc. Methods and apparatuses for a compiler server
US8615750B1 (en) * 2009-06-12 2013-12-24 Adobe Systems Incorporated Optimizing application compiling
CA2698066A1 (en) * 2009-07-31 2011-01-31 Nitobi Software Inc. System and method for remotely compiling multi-platform native applications for mobile devices
US10176270B2 (en) * 2009-12-24 2019-01-08 International Business Machines Corporation Performance of template based javascript widgets
US20110258534A1 (en) * 2010-04-16 2011-10-20 Microsoft Corporation Declarative definition of complex user interface state changes
US20110271248A1 (en) * 2010-04-29 2011-11-03 Microsoft Corporation Converting controls into source code
EP2612235A4 (en) * 2010-09-03 2014-03-05 Siemens Ag Method for parallelizing automatic control programs and compiler
US9026905B2 (en) * 2010-12-17 2015-05-05 Facebook, Inc. Customization of mobile applications using web-based technology
US9092242B2 (en) 2011-01-27 2015-07-28 Hewlett-Packard Development Company, L.P. Computing device to connect to a portable device
US9706006B2 (en) * 2011-07-19 2017-07-11 Infosys Limited System and method of context aware adaption of content for a mobile device
US9489184B2 (en) * 2011-12-30 2016-11-08 Oracle International Corporation Adaptive selection of programming language versions for compilation of software programs
KR101907422B1 (en) 2012-02-10 2018-10-12 한국전자통신연구원 Network Application Combining Development Apparatus and Method, and Server using the same
US9075913B2 (en) 2012-02-27 2015-07-07 Qualcomm Incorporated Validation of applications for graphics processing unit
US8910115B2 (en) * 2012-04-02 2014-12-09 Kony Solutions, Inc. Systems and methods for application development
US9547533B2 (en) * 2012-10-15 2017-01-17 Optum Soft, Inc. Efficient reliable distributed flow-controlled event propagation
US9075833B2 (en) * 2013-01-21 2015-07-07 International Business Machines Corporation Generating XML schema from JSON data
US9395960B2 (en) * 2013-02-19 2016-07-19 PLUMgrid, Inc. Method and system for data plane abstraction to enable a dynamic creation of network applications
US9641590B2 (en) * 2014-08-27 2017-05-02 Google Inc. Resuming session states
US9830307B1 (en) * 2014-12-11 2017-11-28 Amazon Technologies, Inc. Ahead of time compilation of content pages
CA2875850C (en) * 2014-12-23 2022-07-05 Steve Cooper Version synchronization of dependent components
EP3241310B1 (en) 2015-01-02 2019-07-31 Systech Corporation Control infrastructure
US10567517B2 (en) * 2015-06-05 2020-02-18 Apple Inc. Web resource load blocking API
US10120661B2 (en) * 2015-07-16 2018-11-06 Sugarcrm Inc. Multi-flavored software execution from a singular code base
US10061629B2 (en) 2015-07-22 2018-08-28 Optumsoft, Inc. Compact binary event log generation
CN105068855B (en) * 2015-08-19 2021-06-18 北京奇虎科技有限公司 Method, server and system for compiling android package development file
US10140105B2 (en) * 2016-03-10 2018-11-27 Wowza Media Systems, LLC Converting source code
US10419568B2 (en) * 2016-04-01 2019-09-17 Microsoft Technology Licensing, Llc Manipulation of browser DOM on server
EP3229397B1 (en) * 2016-04-07 2020-09-09 ContactOffice Group Method for fulfilling a cryptographic request requiring a value of a private key
US10831637B2 (en) 2016-04-23 2020-11-10 International Business Machines Corporation Warning data management with respect to an execution phase
US10977017B2 (en) * 2016-04-23 2021-04-13 International Business Machines Corporation Warning data management for distributed application development
US10671038B2 (en) 2016-07-15 2020-06-02 Fisher-Rosemount Systems, Inc. Architecture-independent process control
CN108259332B (en) * 2016-12-28 2021-04-02 航天信息股份有限公司 Message transmission method and system based on FSMP
TWI648608B (en) * 2017-03-20 2019-01-21 台達電子工業股份有限公司 Intelligent finite-state machine remote control system for air-condition equipment
CN107193625A (en) * 2017-07-26 2017-09-22 郑州云海信息技术有限公司 A kind of processing method and processing device of script file
EP3470103A1 (en) 2017-10-10 2019-04-17 Air Liquide Medical Systems Elbow connector for respiratory mask with a mesh structure for venting gas expired by the patient
US11216255B1 (en) * 2017-12-30 2022-01-04 ezbds, LLC Open compiler system for the construction of safe and correct computational systems
US11531947B2 (en) * 2018-10-19 2022-12-20 Oracle International Corporation System and method for software development including column-based process editor
CN112199219A (en) * 2020-11-17 2021-01-08 南开大学 Cross-language operation remote calling method
CN113342356B (en) * 2021-05-18 2023-03-28 浪潮软件股份有限公司 Client framework operation and management configuration method
US11461080B1 (en) 2021-06-07 2022-10-04 Snowflake Inc. Inline compilation of user defined functions
CN113703772A (en) * 2021-08-23 2021-11-26 北京计算机技术及应用研究所 Efficient intelligent computing application architecture of heterogeneous platform based on ICE (Internet communications Engineers) and construction method thereof

Citations (40)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4667290A (en) * 1984-09-10 1987-05-19 501 Philon, Inc. Compilers using a universal intermediate language
US5943424A (en) * 1996-06-17 1999-08-24 Hewlett-Packard Company System, method and article of manufacture for processing a plurality of transactions from a single initiation point on a multichannel, extensible, flexible architecture
US6003038A (en) * 1997-03-31 1999-12-14 Sun Microsystems, Inc. Object-oriented processor architecture and operating method
US6209124B1 (en) * 1999-08-30 2001-03-27 Touchnet Information Systems, Inc. Method of markup language accessing of host systems and data using a constructed intermediary
US6226675B1 (en) * 1998-10-16 2001-05-01 Commerce One, Inc. Participant server which process documents for commerce in trading partner networks
US6244545B1 (en) * 1999-06-18 2001-06-12 Lockheed Martin Corporation Snap-on wire guide
US6286134B1 (en) * 1999-04-23 2001-09-04 Sun Microsystems, Inc. Instruction selection in a multi-platform environment
US6341372B1 (en) * 1997-05-01 2002-01-22 William E. Datig Universal machine translator of arbitrary languages
US6343310B1 (en) * 1996-03-28 2002-01-29 Dirienzo Andrew L. Attachment integrated claims system and operating method therefor
US6389590B1 (en) * 1999-06-22 2002-05-14 Microsoft Corporation Indefinite-size variables within an intermediate language
US6526570B1 (en) * 1999-04-23 2003-02-25 Sun Microsystems, Inc. File portability techniques
US6539396B1 (en) * 1999-08-31 2003-03-25 Accenture Llp Multi-object identifier system and method for information service pattern environment
US6542912B2 (en) * 1998-10-16 2003-04-01 Commerce One Operations, Inc. Tool for building documents for commerce in trading partner networks and interface definitions based on the documents
US6550057B1 (en) * 1999-08-31 2003-04-15 Accenture Llp Piecemeal retrieval in an information services patterns environment
US6601234B1 (en) * 1999-08-31 2003-07-29 Accenture Llp Attribute dictionary in a business logic services environment
US6615235B1 (en) * 1999-07-22 2003-09-02 International Business Machines Corporation Method and apparatus for cache coordination for multiple address spaces
US6629313B1 (en) * 2000-06-29 2003-09-30 Microsoft Corporation In-line database access statements without a pre-compiler
US6640244B1 (en) * 1999-08-31 2003-10-28 Accenture Llp Request batcher in a transaction services patterns environment
US6640238B1 (en) * 1999-08-31 2003-10-28 Accenture Llp Activity component in a presentation services patterns environment
US6643652B2 (en) * 2000-01-14 2003-11-04 Saba Software, Inc. Method and apparatus for managing data exchange among systems in a network
US6651248B1 (en) * 2000-09-01 2003-11-18 International Business Machines Corporation Method and apparatus for efficient interface method dispatch
US6766511B1 (en) * 2000-07-10 2004-07-20 International Business Machines Corporation Apparatus and method for performing symbolic resolution of modules using static representations of a trace
US6772165B2 (en) * 2000-05-16 2004-08-03 O'carroll Garrett Electronic document processing system and method for merging source documents on a node-by-node basis to generate a target document
US6836883B1 (en) * 2000-06-21 2004-12-28 Microsoft Corporation Method and system for compiling multiple languages
US6842906B1 (en) * 1999-08-31 2005-01-11 Accenture Llp System and method for a refreshable proxy pool in a communication services patterns environment
US6842894B1 (en) * 1999-04-05 2005-01-11 Gateway, Inc. Dynamic Compiling
US6886169B2 (en) * 2002-11-19 2005-04-26 Nexaweb Technologies, Inc. System and method for stateful web-based computing
US6898618B1 (en) * 2000-05-09 2005-05-24 Sun Microsystems, Inc. Client-specified display services in a distributed computing environment
US6918107B2 (en) * 2001-07-02 2005-07-12 Bea Systems, Inc. Programming language extensions for processing data representation language objects and related applications
US20050155027A1 (en) * 2004-01-09 2005-07-14 Wei Coach K. System and method for developing and deploying computer applications over a network
US6950848B1 (en) * 2000-05-05 2005-09-27 Yousefi Zadeh Homayoun Database load balancing for multi-tier computer systems
US6968503B1 (en) * 2000-03-09 2005-11-22 Quovadx, Inc. XML user interface for a workflow server
US6971084B2 (en) * 2001-03-02 2005-11-29 National Instruments Corporation System and method for synchronizing execution of a batch of threads
US6981250B1 (en) * 2001-07-05 2005-12-27 Microsoft Corporation System and methods for providing versioning of software components in a computer programming language
US6988263B1 (en) * 2000-07-10 2006-01-17 International Business Machines Corporation Apparatus and method for cataloging symbolic data for use in performance analysis of computer programs
US7093243B2 (en) * 2002-10-09 2006-08-15 International Business Machines Corporation Software mechanism for efficient compiling and loading of java server pages (JSPs)
US7111282B2 (en) * 2001-06-12 2006-09-19 Hewlett-Packard Development Company, L.P. Instrumenting a software program and collecting data from the instrumented software program by type
US7117504B2 (en) * 2001-07-10 2006-10-03 Microsoft Corporation Application program interface that enables communication for a network software platform
US7165239B2 (en) * 2001-07-10 2007-01-16 Microsoft Corporation Application program interface for network software platform
US7246146B1 (en) * 1999-11-18 2007-07-17 International Business Machines Corporation Legacy host system hot link modeling and navigation

Family Cites Families (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH04243429A (en) * 1991-01-17 1992-08-31 Nec Corp Compiler
IL100986A (en) * 1991-02-27 1997-01-10 Digital Equipment Corp Method for compiling code
JPH05346858A (en) * 1992-06-12 1993-12-27 Sony Corp Program editing method
JPH07121379A (en) * 1993-10-28 1995-05-12 Nec Software Ltd Plural languages mixing compiler
US5812850A (en) * 1995-11-13 1998-09-22 Object Technology Licensing Corp. Object-oriented symbolic debugger using a compiler driven database and state modeling to control program execution
US5848274A (en) * 1996-02-29 1998-12-08 Supercede, Inc. Incremental byte code compilation system
JPH10333917A (en) * 1997-05-28 1998-12-18 Nec Software Ltd Distributed compilation system
US6029000A (en) * 1997-12-22 2000-02-22 Texas Instruments Incorporated Mobile communication system with cross compiler and cross linker
JPH11353189A (en) * 1998-04-30 1999-12-24 Fuondotto Comu Japan Kk Method and device for implementing tag-based display language using procedure instruction language
JPH11328138A (en) * 1998-05-20 1999-11-30 Hitachi Ltd Distributed computer system
US6484312B1 (en) * 1999-06-07 2002-11-19 Microsoft Corporation Inferring operand types within an intermediate language
JP4042280B2 (en) * 1999-12-21 2008-02-06 富士ゼロックス株式会社 Execution program generation method and execution program generation apparatus, execution program execution method, and computer-readable program storage medium
JP2002182915A (en) * 2000-12-19 2002-06-28 Tokio Marine & Fire Insurance Co Ltd Source program storage method, its system, source program restoring method and system, and compiling method and device
PT1356381E (en) * 2001-02-02 2016-02-22 Opentv Inc A method and apparatus for the compilation of an interpretative language for interactive television

Patent Citations (41)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4667290A (en) * 1984-09-10 1987-05-19 501 Philon, Inc. Compilers using a universal intermediate language
US6343310B1 (en) * 1996-03-28 2002-01-29 Dirienzo Andrew L. Attachment integrated claims system and operating method therefor
US5943424A (en) * 1996-06-17 1999-08-24 Hewlett-Packard Company System, method and article of manufacture for processing a plurality of transactions from a single initiation point on a multichannel, extensible, flexible architecture
US6003038A (en) * 1997-03-31 1999-12-14 Sun Microsystems, Inc. Object-oriented processor architecture and operating method
US6341372B1 (en) * 1997-05-01 2002-01-22 William E. Datig Universal machine translator of arbitrary languages
US6226675B1 (en) * 1998-10-16 2001-05-01 Commerce One, Inc. Participant server which process documents for commerce in trading partner networks
US6542912B2 (en) * 1998-10-16 2003-04-01 Commerce One Operations, Inc. Tool for building documents for commerce in trading partner networks and interface definitions based on the documents
US6842894B1 (en) * 1999-04-05 2005-01-11 Gateway, Inc. Dynamic Compiling
US6526570B1 (en) * 1999-04-23 2003-02-25 Sun Microsystems, Inc. File portability techniques
US6286134B1 (en) * 1999-04-23 2001-09-04 Sun Microsystems, Inc. Instruction selection in a multi-platform environment
US6244545B1 (en) * 1999-06-18 2001-06-12 Lockheed Martin Corporation Snap-on wire guide
US6389590B1 (en) * 1999-06-22 2002-05-14 Microsoft Corporation Indefinite-size variables within an intermediate language
US6615235B1 (en) * 1999-07-22 2003-09-02 International Business Machines Corporation Method and apparatus for cache coordination for multiple address spaces
US6209124B1 (en) * 1999-08-30 2001-03-27 Touchnet Information Systems, Inc. Method of markup language accessing of host systems and data using a constructed intermediary
US6539396B1 (en) * 1999-08-31 2003-03-25 Accenture Llp Multi-object identifier system and method for information service pattern environment
US6550057B1 (en) * 1999-08-31 2003-04-15 Accenture Llp Piecemeal retrieval in an information services patterns environment
US6601234B1 (en) * 1999-08-31 2003-07-29 Accenture Llp Attribute dictionary in a business logic services environment
US6640244B1 (en) * 1999-08-31 2003-10-28 Accenture Llp Request batcher in a transaction services patterns environment
US6640238B1 (en) * 1999-08-31 2003-10-28 Accenture Llp Activity component in a presentation services patterns environment
US6842906B1 (en) * 1999-08-31 2005-01-11 Accenture Llp System and method for a refreshable proxy pool in a communication services patterns environment
US7246146B1 (en) * 1999-11-18 2007-07-17 International Business Machines Corporation Legacy host system hot link modeling and navigation
US6643652B2 (en) * 2000-01-14 2003-11-04 Saba Software, Inc. Method and apparatus for managing data exchange among systems in a network
US6968503B1 (en) * 2000-03-09 2005-11-22 Quovadx, Inc. XML user interface for a workflow server
US6950848B1 (en) * 2000-05-05 2005-09-27 Yousefi Zadeh Homayoun Database load balancing for multi-tier computer systems
US6898618B1 (en) * 2000-05-09 2005-05-24 Sun Microsystems, Inc. Client-specified display services in a distributed computing environment
US6772165B2 (en) * 2000-05-16 2004-08-03 O'carroll Garrett Electronic document processing system and method for merging source documents on a node-by-node basis to generate a target document
US6836883B1 (en) * 2000-06-21 2004-12-28 Microsoft Corporation Method and system for compiling multiple languages
US6629313B1 (en) * 2000-06-29 2003-09-30 Microsoft Corporation In-line database access statements without a pre-compiler
US6988263B1 (en) * 2000-07-10 2006-01-17 International Business Machines Corporation Apparatus and method for cataloging symbolic data for use in performance analysis of computer programs
US6766511B1 (en) * 2000-07-10 2004-07-20 International Business Machines Corporation Apparatus and method for performing symbolic resolution of modules using static representations of a trace
US6651248B1 (en) * 2000-09-01 2003-11-18 International Business Machines Corporation Method and apparatus for efficient interface method dispatch
US6971084B2 (en) * 2001-03-02 2005-11-29 National Instruments Corporation System and method for synchronizing execution of a batch of threads
US7111282B2 (en) * 2001-06-12 2006-09-19 Hewlett-Packard Development Company, L.P. Instrumenting a software program and collecting data from the instrumented software program by type
US6918107B2 (en) * 2001-07-02 2005-07-12 Bea Systems, Inc. Programming language extensions for processing data representation language objects and related applications
US6981250B1 (en) * 2001-07-05 2005-12-27 Microsoft Corporation System and methods for providing versioning of software components in a computer programming language
US7117504B2 (en) * 2001-07-10 2006-10-03 Microsoft Corporation Application program interface that enables communication for a network software platform
US7165239B2 (en) * 2001-07-10 2007-01-16 Microsoft Corporation Application program interface for network software platform
US7093243B2 (en) * 2002-10-09 2006-08-15 International Business Machines Corporation Software mechanism for efficient compiling and loading of java server pages (JSPs)
US6886169B2 (en) * 2002-11-19 2005-04-26 Nexaweb Technologies, Inc. System and method for stateful web-based computing
US20050155027A1 (en) * 2004-01-09 2005-07-14 Wei Coach K. System and method for developing and deploying computer applications over a network
US7614052B2 (en) * 2004-01-09 2009-11-03 Nexaweb Technologies Inc. System and method for developing and deploying computer applications over a network

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
Lin, "Architecture for XML Binding (JAXB): A Primer", 3-2002, http://java.sun.com/developer/technicalArticles/xml/jaxb/, Sun Microsystems, Inc., 4 pages. *
Sam Brodkin, "Use XML data binding to do your laundry", 12-2001, Javaworld, 11 pages. *
Sun Microsystems, "The Java(TM) Architecture for XML Binding (JAXB)", 9-2002, Sun Microsystems, Inc., 188 pages. *

Cited By (34)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10552520B2 (en) 2002-09-10 2020-02-04 Sqgo Innovations, Llc System and method for provisioning a mobile software application to a mobile device
US10372796B2 (en) 2002-09-10 2019-08-06 Sqgo Innovations, Llc Methods and systems for the provisioning and execution of a mobile software application
US10810359B2 (en) 2002-09-10 2020-10-20 Sqgo Innovations, Llc System and method for provisioning a mobile software application to a mobile device
US10831987B2 (en) 2002-09-10 2020-11-10 Sqgo Innovations, Llc Computer program product provisioned to non-transitory computer storage of a wireless mobile device
US9390191B2 (en) 2002-09-10 2016-07-12 SQGo, LLC Methods and systems for the provisioning and execution of a mobile software application
US9342492B1 (en) 2002-09-10 2016-05-17 SQGo, LLC Methods and systems for the provisioning and execution of a mobile software application
US9311284B2 (en) 2002-09-10 2016-04-12 SQGo, LLC Methods and systems for enabling the provisioning and execution of a platform-independent application
US10839141B2 (en) 2002-09-10 2020-11-17 Sqgo Innovations, Llc System and method for provisioning a mobile software application to a mobile device
US10387549B2 (en) 2004-06-25 2019-08-20 Apple Inc. Procedurally expressing graphic objects for web pages
US9477646B2 (en) 2004-06-25 2016-10-25 Apple Inc. Procedurally expressing graphic objects for web pages
US20060005114A1 (en) * 2004-06-25 2006-01-05 Richard Williamson Procedurally expressing graphic objects for web pages
US8239749B2 (en) * 2004-06-25 2012-08-07 Apple Inc. Procedurally expressing graphic objects for web pages
US8108787B2 (en) * 2005-07-01 2012-01-31 Microsoft Corporation Distributing input events to multiple applications in an interactive media environment
US20070002045A1 (en) * 2005-07-01 2007-01-04 Microsoft Corporation Rendering and compositing multiple applications in an interactive media environment
US8305398B2 (en) 2005-07-01 2012-11-06 Microsoft Corporation Rendering and compositing multiple applications in an interactive media environment
US8656268B2 (en) 2005-07-01 2014-02-18 Microsoft Corporation Queueing events in an interactive media environment
US20070005758A1 (en) * 2005-07-01 2007-01-04 Microsoft Corporation Application security in an interactive media environment
US8799757B2 (en) 2005-07-01 2014-08-05 Microsoft Corporation Synchronization aspects of interactive multimedia presentation management
US8020084B2 (en) 2005-07-01 2011-09-13 Microsoft Corporation Synchronization aspects of interactive multimedia presentation management
US7941522B2 (en) 2005-07-01 2011-05-10 Microsoft Corporation Application security in an interactive media environment
US20070006061A1 (en) * 2005-07-01 2007-01-04 Microsoft Corporation Synchronization aspects of interactive multimedia presentation management
US20070005757A1 (en) * 2005-07-01 2007-01-04 Microsoft Corporation Distributing input events to multiple applications in an interactive media environment
US20100023955A1 (en) * 2008-07-28 2010-01-28 Marcottage Method and system and apparatus for dynamic software environment
US20120001921A1 (en) * 2009-01-26 2012-01-05 Escher Marc System and method for creating, managing, sharing and displaying personalized fonts on a client-server architecture
US20100251231A1 (en) * 2009-03-25 2010-09-30 Microsoft Corporation Device dependent on-demand compiling and deployment of mobile applications
US8667483B2 (en) 2009-03-25 2014-03-04 Microsoft Corporation Device dependent on-demand compiling and deployment of mobile applications
US20100293499A1 (en) * 2009-05-14 2010-11-18 Microsoft Corporation Rendering to a device desktop of an adaptive input device
US20100299626A1 (en) * 2009-05-20 2010-11-25 Microsoft Corporation Systems and Methods of Providing Rich User Interface and Animation to Auxiliary Display Devices
US10346521B2 (en) 2010-09-10 2019-07-09 Facebook, Inc. Efficient event delegation in browser scripts
US9740669B2 (en) * 2010-09-10 2017-08-22 Facebook, Inc. Efficient event delegation in browser scripts
US20150178254A1 (en) * 2010-09-10 2015-06-25 Facebook, Inc. Efficient Event Delegation In Browser Scripts
US10417036B2 (en) * 2017-02-24 2019-09-17 Oracle International Corporation Evaluation techniques for fast access to structured, semi-structured and unstructured data using a virtual machine that provides support for dynamic code generation
US10817492B2 (en) * 2017-05-05 2020-10-27 Servicenow, Inc. Application extension
US11360976B2 (en) 2017-08-31 2022-06-14 Oracle International Corporation Deployment of javascript and typescript stored procedures and user-defined functions into database management systems

Also Published As

Publication number Publication date
EP1588230A2 (en) 2005-10-26
US7707563B2 (en) 2010-04-27
WO2004063900A2 (en) 2004-07-29
JP2007524875A (en) 2007-08-30
US20040143823A1 (en) 2004-07-22
EP1588230A4 (en) 2008-05-07
WO2004063900A3 (en) 2007-05-31

Similar Documents

Publication Publication Date Title
US7707563B2 (en) System and method for network-based computing
US7321918B2 (en) Server-side control objects for processing client-side user interface elements
US7614052B2 (en) System and method for developing and deploying computer applications over a network
KR100574156B1 (en) Accessing legacy applications from the internet
US7917888B2 (en) System and method for building multi-modal and multi-channel applications
US8095565B2 (en) Metadata driven user interface
US8578333B2 (en) Method and system for client-side user interface enhancement to enable application integration and portalisation
US8832181B2 (en) Development and deployment of mobile and desktop applications within a flexible markup-based distributed architecture
US9992268B2 (en) Framework for thin-server web applications
US7853884B2 (en) Control-based graphical user interface framework
US20020101448A1 (en) Generating a declarative user interface
US20140143310A1 (en) Method and system for creating it-oriented server-based web applications
US20080168430A1 (en) Open controls
US20060041890A1 (en) Portal runtime framework
KR100831393B1 (en) Presentation method for web applications and web application development system using the same
KR20230036670A (en) Web Application Development System
KR20050034237A (en) Web sheet component for enhancemant of developing performance of business application using by active-x
CHAPTER Flex Integration with J2EE
Hackborn Interactive HTML
IL199860A (en) Method and system for creating it-oriented server-based web applications

Legal Events

Date Code Title Description
STCB Information on status: application discontinuation

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

AS Assignment

Owner name: MONTAGE CAPITAL, LLC, CALIFORNIA

Free format text: SECURITY AGREEMENT;ASSIGNOR:NEXAWEB TECHNOLOGIES, INC.;REEL/FRAME:028768/0643

Effective date: 20120808

AS Assignment

Owner name: NEXAWEB TECHNOLOGIES, INC., MASSACHUSETTS

Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:MONTAGE CAPITAL, LLC;REEL/FRAME:032165/0958

Effective date: 20140131