Socket-like communication API for C

• US 7,580,915 B2
• Filed: 12/14/2004
• Issued: 08/25/2009
• Est. Priority Date: 12/14/2004
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Luik, Oliver, Braun, Bernhard
• Primary Examiner(s): Y; Truong Cam
• Assistant Examiner(s): Hwa; Shyue Jiunn
• Application Number:
  US11/013,278
• Publication Number:
  US 20060129512A1
• Time in Patent Office: 1,715 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: G06F 9/544 Buffers; Shared memory; Pipes

Abstract

A system and method are described for performing data processing using shared memory and socket-like application programming interface. In one embodiment, a plurality of handles is employed and associated with a plurality of processes. The plurality of handles may serve as communication end-points for communication of data. Further, an application programming interface is employed to present the plurality of handles as the application programming interface for sockets for facilitating the communication of data compatible with a programming language.

Claims

1. A method comprising:

integrating at an application server first processes and second processes via a communication system of the application server, the communication system having a shared memory, the first processes including specialized processes of an operating system of the application server, and the second processes including specialized processes of the operating system, the first processes and the second processes are independent of each other, the first processes executing first transactions via a first programming engine of the application server, and the second processes executing second transactions via a second programming engine of the application server, wherein the first transactions are independent of the second transactions,

facilitating bi-directional and unduplicated communication between the first and second processes via sockets of the shared memory, the sockets of shared memory serving as a common communication interface for the first and second processes when communicating bi-directionally,

wherein at least one socket of the sockets is associated with each of the first and second processes, and the sockets are further to serve as a user interface to expose the first and second processes to a user;

creating a handle to serve as a communication end-point for communication of data via the shared memory;

the application server providing to a client system an application programming interface (API) for accessing the handle, wherein the API is presented to the client system as the API for accessing a socket;

wherein the communication interface and API for accessing the handle comprise one or more a C-based interface, a C++-based interface, a C#-based interface, a Visual Basic-based interface, and a Java-based interface;

receiving at a network communication manager of the application server the client request via the provided API for accessing the handle; and

sending the received client request from the network communication manager of the application server to one of the first programming engine and second programming engine via the shared memory,

wherein each of the first and second programming engines is associated with a programming language, wherein the first programming engine includes an Advanced Business Application Programming (ABAP) engine, and the second programming engine includes a Java 2 Enterprise Edition (J2EE) engine, wherein the first transactions include ABAP-related transactions, and the second transactions include Java-related transactions.

2. A system comprising:

a server having a processor and a storage medium coupled with the processor, the server further having an application server, the application server to integrate first processes and second processes via a communication system of the application server, the communication system having a shared memory, the first processes including specialized processes of an operating system of the application server, and the second processes including specialized processes of the operating system, the first processes and the second processes are independent of each other, the first processes executing first transactions via a first programming engine of the application server, and the second processes executing second transactions via a second programming engine of the application server, wherein the first transactions are independent of the second transactions;

the application server further to facilitate bi-directional and unduplicated communication between the first and second processes via sockets of the shared memory, the sockets of shared memory serving as a common communication interface for the first and second processes when communicating bi-directionally,

wherein at least one socket of the sockets is associated with each of the first and second processes, and the sockets are further to serve as a user interface to expose the first and second processes to a user the application server further to create a handle to serve as a communication end-point for communication of data via the shared memory, the application server further to provide to a client system an application programming interface (API) for accessing the handle, wherein the API is presented to the client system as an API for accessing a socket;

wherein the communication interface and API for accessing the handle comprise one or more of a C-based interface, a C++-based interface, a C#-based interface, a Visual Basic-based interface, and a Java-based interface;

a network communication manager of the application server to receive a client request via the provided API for accessing the handle, the network communication manager further to send the received client request to one of the first programming engine and second programming engine via the shared memory,

wherein each of the first and second programming engines is associated with a programming language, wherein the first programming engine includes an Advanced Business Application Programming (ABAP) engine, and the second programming engine includes a Java 2 Enterprise Edition (J2EE) engine, wherein the first transactions include ABAP-related transactions and Java-related transactions.

3. A machine-readable storage medium comprising instructions which, when executed, cause a machine to perform a method comprising:

integrating at an application server first processes and second processes via a communication system of the application server, the communication system having a shared memory, the first processes including specialized processes of an operating system of the application server, and the second processes including specialized processes of the operating system, the first processes and the second processes are independent of each other, the first processes executing first transactions via a first programming engine of the application server, and the second processes executing second transactions via a second programming engine of the application server, wherein the first transactions are independent of the second transactions;

facilitate bi-directional and unduplicated communication between the first and second processes via sockets of the shared memory, the sockets of shared memory serving as a common communication interface for the first and second processes when communicating bi-directionally,

wherein at least one socket of the sockets is associated with each of the first and second processes, and the sockets are further to serve as a user interface to expose the first and second processes to a user;

creating a handle to serve as a communication end-point for communication of data via the shared memory;

the application server providing to a client system an application programming interface (API) for accessing the handle, wherein the API is presented to the client system as the API for accessing a socket;

wherein the communication interface and API for accessing the handle comprise one or more of a C-based interface, a C++-based interface, a C#-based interface, a Visual Basic-based interface, and a Java-based interface;

receiving at a network communication manager of the application server the client request via the provided API for accessing the handle; and

sending the received client request from the network communication manager of the application server to one of the first programming engine and second programming engine via the shared memory,

wherein each of the first and second programming engines is associated with a programming language, wherein the first programming engine includes an Advanced Business Application Programming (ABAP) engine, and the second programming engine includes a Java 2 Enterprise Edition (J2EE) engine, wherein the first transactions include ABAP-related transactions, and the second transactions include Java-related transactions.