Universal interprocess communication achieving method

Abstract

Present invention relates to implementation method between progress communication for providing universal progress realizing data format application freeness. Present invention includes starting up service end service, client-side calling service, packing and sequencing parameter, packing called correlated data message to information packet without categorical data, service end processing calling, unpackage received information packet, after extracting out packing data and processing repackaging to information packet without categorical data and feeding back, client-side unpackaging return message, after extraction data covering calling parameter numeric value, service end closing service. Through design a universal, simple data to package Windows progress functional calling details, to raise programming exploitation efficiency. Present invention is suitable for calling side and service provider, avoiding protocol compatibility version problem between service end and client-side with wide use range.

Description

technical field [0001] The invention relates to a method for realizing inter-process communication. More specifically, the present invention relates to a general interprocess communication implementation method that realizes application independence in data format. Background technique [0002] In the Windows 16-bit environment (Windows 3.1 / 3.2), all Windows applications share a single address, and any process can read, write, or even access the contents of this space (including memory belonging to other processes) The data of the system itself may destroy the data segment code of other programs. [0003] For security reasons, each process in the Windows 32 environment has its own address space, and a WIN32 process cannot access the memory data of another process. Two processes can be addressed with a pointer with the same value, but will be mapped to different physical addresses. What is read and written is only their respective data, which reduces the mutual interferenc...

AI Technical Summary

Problems solved by technology

Defect: The server must run on Windows NT / 2000 / XP

[0020] 2. The serialization of parameters related to the interface, the universality of the interface and the ease of use are not considered

None of these are implemented in standard IPC communication methods

[0022] 3. Efficiency and concurrent calls are not considered

[0024] In this case, simply using shared memory, DDE and other modes cannot solve the problem of concurrent call memory usage conflicts

And we know that the message pipeline mode has the problem of server-side application Windows operating system version restrictions.

Images