Methods and systems for simplifying object mapping for external interfaces

• US 8,983,984 B2
• Filed: 12/13/2013
• Issued: 03/17/2015
• 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 T
• Application Number:
  US14/106,427
• Publication Number:
  US 20140108511A1
• Time in Patent Office: 459 Days
• Field of Search: 707/738, 707/756, 707/802
• US Class Current: 707/756
• 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 external interfaces. At least two client requests for action may be received from an external interface wherein each client request may be evaluated sequentially or concurrently in a governed and non-blocking technique. Each client request may be associated to a logical object in order to minimize a representational gap between the client request and a physical object using the logical object. Each query request may be responded to using the object relational mapping in order to simplify the external interface by minimizing the representational gap between the external interface and the physical object using the logical object.

Claims

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

performing processing associated with receiving at least two client requests for action from an external interface, the external interface comprising a human being or a computer program, wherein the at least two client requests are combined in an application dialogue language (ADL) script, wherein each client request is evaluated sequentially or concurrently in a governed and non-blocking technique;

performing processing associated with associating each client request to a logical object in order to minimize a representational gap between the client request and a physical object using the logical object, wherein the associating comprises accepting an entity identifier and a property name and validating that the client request is a query request, wherein the logical object comprises a dialogue process and a collection of metadata that describes an entity definition, wherein the dialogue process comprises a query subroutine comprising the query request and processing the query request to return a dialogue response, wherein the dialogue response comprises a list of dialogue records of corresponding values from the physical object if a successful query occurs, and a redirection is returned if a non-successful recoverable query occurs, wherein the dialogue response also comprises a value comprising;

value, exception, or the redirection, wherein the redirection is constructed with the entity identifier to a new dialogue model that can be used to recover from an error;

performing processing associated with converting the logical object to a physical object that resides in an object relational mapping using information from the query request;

performing processing associated with mapping between the physical object that resides in the object relational mapping and a database; and

performing processing associated with responding to each query request using the object relational mapping in order to simplify the external interface by minimizing the representational gap between the external interface and the physical object using the logical object.

2. The method of claim 1, wherein the ADL comprises an evaluator configured to evaluate the client request.

3. The method of claim 2, wherein the ADL further comprises a scheduler configured to schedule any sub-routines in the client request.

4. The method of claim 3, wherein:

the evaluator passes the client request to the scheduler; and

the scheduler schedules the sub-routines in the client request.

5. The method of claim 3, wherein the ADL further comprises a governor to prevent any one session from abusing a resource.

6. The method of claim 5, wherein abusing the resource comprises violating a security constraint, exceeding a resource capacity, or a combination thereof.

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 ADL comprises a non-blocking design.

9. The method of claim 1, wherein the ADL is in communication with one or more web services.

10. The method of claim 9, wherein the computer system comprises the web services.

11. The method of claim 9, wherein the web services are housed in a remote computer, and the ADL is configured to communicate with the web services via a network.

12. The method of claim 1, wherein the multiple client requests are performed using the ADL efficiently and without security or resource violations.

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

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

SQL, ASCII, or XML, or any combination thereof.

15. The method of claim 1, wherein the dialogue process further comprises a subroutine comprising:

read, write, method, or navigate, or any combination thereof.

16. The method of claim 1, wherein the dialogue response is a dialogue record of corresponding values from the physical object if a successful read occurs;

and a redirection is returned if a non-successful recoverable read occurs.

17. The method of claim 1, wherein the dialogue response is a dialogue record of corresponding values from the physical object if a successful write occurs;

and a redirection is returned if a non-successful recoverable write occurs.

18. The method of claim 1, wherein the dialogue response is a dialogue record of corresponding values from the physical object if a successful method occurs;

and a redirection is returned if a non-successful recoverable method occurs.

19. The method of claim 1, wherein the dialogue response is a redirection if a successful navigate occurs;

and an exception is returned if a non-successful navigate occurs.

20. The method of claim 1, wherein the physical object comprises a collection of data or logic.

33. The method of claim 1, wherein the dialogue process further comprises a subroutine comprising:

read, write, method, or navigate, or any combination thereof.

34. The method of claim 33, wherein the subroutine further comprises:

performing processing associated with returning a dialogue response.

35. The method of claim 34, wherein the dialogue response includes a combination of value, exception, or redirection.

36. The system of claim 1, wherein the dialogue process further comprises a subroutine comprising:

read, write, method, or navigate, or any combination thereof.

37. The system of claim 36, wherein the subroutine further comprises:

performing processing associated with returning a dialogue response.

38. The method of claim 37, wherein the dialogue response includes a combination of value, exception, or redirection.

21. A system for simplifying object mapping for external interfaces for a computer system, comprising:

a processor in communication with a database, the processor configured for;

performing processing associated with receiving at least two client requests for action from an external interface, the external interface comprising a human being or a computer program, wherein the at least two client requests are combined in an application dialogue language (ADL) script, wherein each client request is evaluated sequentially or concurrently in a governed and non-blocking technique;

performing processing associated with associating each client request to a logical object in order to minimize a representational gap between the client request and a physical object using the logical object, wherein the associating comprises accepting an entity identifier and a property name and validating that the client request is a query request, wherein the logical object comprises a dialogue process and a collection of metadata that describes an entity definition, wherein the dialogue process comprises a query subroutine comprising the query request and processing the query request to return a dialogue response, wherein the dialogue response comprises a list of dialogue records of corresponding values from the physical object if a successful query occurs, and a redirection is returned if a non-successful recoverable query occurs, wherein the dialogue response also comprises a value comprising;

value, exception, or the redirection, wherein the redirection is constructed with the entity identifier to a new dialogue model that can be used to recover from an error;

performing processing associated with converting the logical object to a physical object that resides in an object relational mapping using information from the query request;

performing processing associated with mapping between the physical object that resides in the object relational mapping and a database; and

performing processing associated with responding to each query request using the object relational mapping in order to simplify the external interface by minimizing the representational gap between the external interface and the physical object using the logical object.

22. The system of claim 21, wherein the ADL comprises an evaluator configured to evaluate the client request.

23. The system of claim 22, wherein the ADL further comprises a scheduler configured to schedule any sub-routines in the client request.

24. The system of claim 23, wherein:

the evaluator passes the client request to the scheduler; and

the scheduler schedules the sub-routines in the client request.

25. The system of claim 23, wherein the ADL further comprises a governor to prevent any one session from abusing a resource.

26. The system of claim 25, wherein abusing the resource comprises violating a security constraint, exceeding a resource capacity, or a combination thereof.

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

28. The system of claim 21, wherein the ADL comprises a non-blocking design.

29. The system of claim 21, wherein the ADL is in communication with one or more web services.

30. The system of claim 29, wherein the computer system comprises the web services.

31. The system of claim 29, wherein the web services are housed in a remote computer, and the ADL is configured to communicate with the web services via a network.

32. The system of claim 21, wherein the multiple client requests are performed using the ADL efficiently and without security or resource violations.

39. The system of claim 21, wherein the database comprises formatted text.

40. The system of claim 21, wherein the database comprises:

SQL, ASCII, or XML, or any combination thereof.

41. The system of claim 21, wherein the dialogue process further comprises a subroutine comprising:

read, write, method, or navigate, or any combination thereof.

42. The system of claim 21, wherein the dialogue response is a dialogue record of corresponding values from the physical object if a successful read occurs;

and a redirection is returned if a non-successful recoverable read occurs.

43. The system of claim 21, wherein the dialogue response is a dialogue record of corresponding values from the physical object if a successful write occurs;

and a redirection is returned if a non-successful recoverable write occurs.

44. The system of claim 21, wherein the dialogue response is a dialogue record of corresponding values from the physical object if a successful method occurs;

and a redirection is returned if a non-successful recoverable method occurs.

45. The system of claim 21, wherein the dialogue response is a redirection if a successful navigate occurs;

and an exception is returned if a non-successful navigate occurs.

46. The system of claim 21, wherein the physical object comprises a collection of data or logic.