Methods and systems for simplifying object mapping for user interfaces

• US 10,108,743 B2
• Filed: 01/22/2015
• Issued: 10/23/2018
• Est. Priority Date: 07/02/2009
• Status: Active Grant

• Current Assignee: Hexagon Technology Center GmbH (Hexagon AB)
• Original Assignee: Catavolt, Inc. (Hexagon AB)
• Inventors: Osborne, Glenn W.
• Primary Examiner(s): Truong, Cam-Y
• Application Number:
  US14/603,069
• Publication Number:
  US 20150199451A1
• Time in Patent Office: 1,370 Days
• CPC Class Codes: G06F 16/25 Integrating or interfacing systems involving database management systems
• CPC Class Codes: G06F 16/258 Data format conversion from or to a database
• CPC Class Codes: G06F 16/86 Mapping to a database
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46

Abstract

Methods and systems for simplifying object mapping for user interfaces are described. Client requests can be accepted from the client computers to access a resource of an application dialogue language (ADL). The client requests can be distributed across participating back ends. Each client request can be evaluated by the ADL before an ADL result is returned. If a governor does not detect a violation, expressions can be analyzed to determine whether any expression can be calculated locally by the ADL to produce the ADL result. The ADL result can be associated to a logical object in order to minimize a representational gap between each client request and a physical object. The logical object can be converted to the physical object, and the physical object can be mapped to the relational database. A response to each client request can be produced based on the mapping between the physical object and the relational database.

Claims

1. A method for simplifying object mapping for user interfaces on a computer system, comprising:

accepting, remotely via a network, client requests from client computers via user interfaces;

receiving, by a computer, the client requests, from the client computers, to access a resource of an application dialogue language (ADL), wherein the ADL comprises an evaluator to evaluate the client requests, and wherein the ADL comprises a non-blocking feature which suspends processing until sub-processing is completed and until a pre-defined external event is achieved;

distributing, by the computer, via the networks, the client requests across participating back ends;

evaluating, sequentially or concurrently in a governed and non-blocking technique via calls, by the computer using the ADL, each client request before an ADL result is returned, wherein the ADL comprises a governor to prevent any session related to said each client request from abusing the resource, wherein a session state of the session between the calls to a scripting engine is preserved by requesters, and wherein the ADL supports programming in small abstractions that allows for sub-procedures, looping, and building of expressions from other expressions of the client requests;

if the governor does not detect a violation, analyzing, by the computer, the expressions to determine whether any expression can be calculated locally by the ADL to produce the ADL result;

associating, by the computer based on the ADL result, the ADL to a logical object in order to minimize a representational gap between said each client request and a physical object;

in response to said each client request, converting, by the computer, the logical object to the physical object and mapping the physical object to a relational database; and

producing, by the computer, a response to said each client request based on the mapping between the physical object and the relational database.

2. The method of claim 1, wherein the governor also prevents any one session from sharing a resource.

5. The method of claim 1, wherein the method is multi-tenant friendly.

6. The method of claim 1, wherein abusing the resource comprises violating a security constraint and/or exceeding a resource capacity.

7. The method of claim 1, wherein the ADL runs on top of an application programming interface (API).

8. The method of claim 1, wherein the computer system comprises web services and wherein the ADL is in communication with the web services.

9. The method of claim 1, wherein the database comprises formatted text.

10. The method of claim 1, wherein the database comprises:

Structure Query Language (SQL), American Standard Code for Information Interchange (ASCII), or Extensible Markup Language (XML), or any combination thereof.

11. The method of claim 1, wherein the physical object resides in an object relational mapping.

3. A system for simplifying object mapping for user interfaces, comprising:

a processor configured for;

accepting, remotely via a network, client requests from client computers via user interfaces;

receiving, by a computer, the client requests, from the client computers, to access a resource of an application dialogue language (ADL), wherein the ADL comprises an evaluator to evaluate the client requests, and wherein the ADL comprises a non-blocking feature which suspends processing until sub-processing is completed and until a pre-defined external event is achieved;

distributing, by the computer, via the networks, the client requests across participating back ends;

evaluating, sequentially or concurrently in a governed and non-blocking technique via calls, by the computer, each client request before an ADL evaluation is returned, wherein the ADL comprises a governor to prevent any session related to said each client request from abusing the resource, wherein a session state of the session between the calls to a scripting engine is preserved by requesters, and wherein the ADL supports programming in small abstractions that allows for sub-procedures, looping, and building of expressions from other expressions of the client requests;

if the governor does not detect a violation, analyzing, by the computer, the expressions to determine whether any expression can be calculated locally by the ADL to produce the ADL evaluation;

associating, by the computer based on the ADL evaluation, the ADL to a logical object in order to minimize a representational gap between said each client request and a physical object;

in response to said each client request, converting, by the computer, the logical object to the physical object and mapping the physical object to a relational database; and

producing, by the computer, a response to said each client request based on the mapping between the physical object and the relational database.

4. The system of claim 3, wherein the governor also prevents any one session from sharing a resource.

12. The system of claim 3, wherein the system is multi-tenant friendly.

13. The system of claim 3, wherein abusing the resource comprises violating a security constraint and/or exceeding a resource capacity.

14. The system of claim 3, wherein the ADL runs on top of an application programming interface (API).

15. The system of claim 3, wherein the computer system comprises web services and wherein the ADL is in communication with the web services.

16. The system of claim 3, wherein the database comprises formatted text.

17. The system of claim 3, wherein the database comprises:

Structure Query Language (SQL), American Standard Code for Information Interchange (ASCII), or Extensible Markup Language (XML), or any combination thereof.

18. The system of claim 3, wherein the physical object resides in an object relational mapping.