KR101229264B1 - Common meessage distributor and method for transmitting window message thereof - Google Patents

Abstract

Disclosed is a method of transmitting a window message of a common message distributor connected to at least one module. In accordance with another aspect of the present invention, a method of transmitting a window message includes registering a window handle of a dynamic link library (DLL) module, detecting an event of receiving the window message from the at least one module, and if the event is detected, callback Storing a window message in a queue of the callback function by calling a function; calling a header information interpretation function; analyzing the window message stored in the queue of the callback function; using a result of analyzing the window message The method may include determining a transmission path of the window message and transmitting the window message along the transmission path.

Description

Common Message Splitter and its Window Message Transfer Method {COMMON MEESSAGE DISTRIBUTOR AND METHOD FOR TRANSMITTING WINDOW MESSAGE THEREOF}

The present invention relates to a common message distributor and a window message transmission method, and more particularly, to a common message distributor and a window message transmission method connected to a plurality of modules to transmit a window message to at least one of the plurality of modules. It is about.

As the professionalism and complexity of various programs or applications increase, there are an increasing number of people who co-produce while producing a program or application.

As several people participate in the co-production, the necessity of interworking between production participation modules is increasing, and various middlewares are being developed to satisfy this necessity. Here, middleware refers to software that enables seamless communication between applications and operating environments by interworking heterogeneous hardware or protocols in a distributed computing environment. Examples include HAVI (Home Audio Video Interoperability), JINI, LonWorks, and HnCP ( Home Network Control Protocol (UPNP) and Universal Plug and Play (UPnP).

Meanwhile, in the case of an interface between a plurality of modules in a single system, socket communication or window messages, shared memory, pipelines, etc. provided by an operating system (OS) may be used.

In particular, in the Windows environment, socket communication, shared memory, and window messages are mainly used, and an appropriate communication method can be selected and used according to the interworking object.

On the other hand, when only a small number of people participate in program or application production, even if a plurality of interworking methods are used in a single system, the problem due to the complexity of the system will be weak.

However, in the case where the production of a program or an application is enlarged as in the case of the recent case and a large number of people participate in the production, the complexity of the system may increase rapidly if each of the plurality of people uses heterogeneous interworking methods.

In addition, if multiple personnel each use heterogeneous interworking methods, the software integration process will take considerable time and expense.

In order to solve this problem, it is required to develop a common message distributor that can be commonly used by a large number of people participating in the production.

The present invention has been made in response to the above request and at the same time solves the above-described problem, the present invention provides a common message distributor and a window message transmission method that can be commonly used by a plurality of modules.

According to an aspect of the present invention, there is provided a method of transmitting a window message of a common message distributor connected to at least one module, the method comprising: registering a window handle of a dynamic link library (DLL) module, the window message from the at least one module Detecting an event for receiving the event; if the event is detected, calling a callback function to store the window message in a queue of the callback function; calling a header information interpretation function; and storing the window message in the queue of the callback function. The method may include analyzing a window message, determining a transmission path of the window message using a result of analyzing the window message, and transmitting the window message along the transmission path.

In addition, in order to achieve the above, the present invention is connected to a plurality of modules, the common message distributor for transmitting a window message, the communication unit for receiving a window message from the plurality of modules, the window message and the window message A storage unit for storing a window handle of a dynamic link library (DLL) module including a callback function for storing in a queue and a header information interpretation function for interpreting the window message, the callback function and the header information called from the storage unit The control unit may be configured to determine a transmission destination of the window message by using an analysis function and to control the communication unit to transmit the window message to the determined transmission destination.

According to various embodiments of the present disclosure, a common message distributor and a window message transmission method that can be commonly used by a plurality of modules may be provided, and thus user convenience may be maximized. It also reduces the system complexity that can arise from using heterogeneous protocols between modules.

1 is a conceptual diagram illustrating a relationship between a common message distributor and a plurality of modules connected to a common message distributor according to an embodiment of the present invention.
2 is a detailed internal view of a common message distributor according to an embodiment of the present invention.
3 is a conceptual diagram conceptually illustrating a queue of a callback function.
4 is a flowchart illustrating a window message transmission method of a common message distributor according to an embodiment of the present invention.

Hereinafter, with reference to the accompanying drawings, preferred embodiments of the present invention will be described in more detail. It is to be noted that the same components in the drawings are denoted by the same reference numerals whenever possible. In the following description and the annexed drawings, detailed descriptions of well-known functions and configurations that may unnecessarily obscure the subject matter of the present invention will be omitted.

1 is a conceptual diagram illustrating a relationship between a common message distributor and a plurality of modules 100-1, 100-2, 100-n, 110 connected to a common message distributor 120 according to an embodiment of the present invention.

As shown in FIG. 1, the common message distributor 120 may be wired or wirelessly connected to the plurality of modules 100-1, 100-2, 100-n and the communication module 110.

Each of the plurality of modules 100-1, 100-2, 100-n may be connected to the common message distributor 120 to perform a collaborative operation, and the plurality of modules 100-1, 100-2, 100-n may perform a common task. It may be implemented in the form of an intelligent terminal such as a computer. Meanwhile, each of the plurality of modules 100-1, 100-2, and 100-n may also be implemented in the form of a dummy terminal, and it will be apparent to those skilled in the art that the apparatus for inputting / outputting data to the dummy terminal may be further connected.

Each of the plurality of modules 100-1, 100-2, 100-n may transmit or receive a window message designated to perform a specific task. The window message may include at least one of module information and header information of each module. That is, each of the plurality of modules 100-1, 100-2, 100-n may transmit its module information periodically or aperiodically to the common message distributor 120, and the common message distributor 120 may include a plurality of connected modules ( Information about 100-1,100-2,100-n) may be updated periodically or aperiodically.

As described above, each of the plurality of modules 100-1, 100-2, 100-n may periodically or aperiodically transmit a window message to the common message distributor 120, and the common message distributor 120 may transmit a plurality of modules ( It is also possible to intercept a window message transmitted from each of 100-1,100-2,100-n. The configuration of intercepting the window message may be implemented by calling a callback function, which will be described later in more detail.

In addition, the common message distributor 120 may register a window handle of a dynamic link library (DLL) module. Here, DLL is a dynamic library implemented in Microsoft Windows. Inside the DLL, there are various functions that other programs can call and use. In the case of an extension DLL, there may be a class. Meanwhile, the window handle may be HWND type.

Thereafter, the common message distributor 120 may analyze window messages received from the respective modules 100-1, 100-2, and 100-n to determine a transmission path for transmitting the window messages. The configuration in which the common message distributor 120 analyzes the window message to determine a path to which the window message is transmitted will be described in more detail later.

The common message distributor 120 may transmit the window message according to the path to which the determined window message is to be transmitted. In more detail, the common message distributor 120 may transmit the window message to one of the plurality of modules 100-1, 100-2, and 100-n or the communication module 110.

Here, the communication module 110 may refer to a module that is not directly connected to the plurality of modules 100-1, 100-2, and 100-n. That is, a specific module (for example, 10-1) of the plurality of modules 100-1, 100-2, 100-n is a network other than the other modules 10-2, 10-n except for the specific module 10-1. When the window message needs to be transmitted to the outside, the common message distributor 120 may transmit the window message to the communication module 110 capable of transmitting the window message to the outside.

As described above, the common message distributor 120 may receive or intercept all of the window messages transmitted from the plurality of modules 100-1, 100-2, and 100-n, thereby facilitating the modules 100-1, 100-2, 100. -n) can increase compatibility. In addition, the common message distributor 120 may transmit the window message to the outside of the connected modules 100-1, 100-2, and 100-n using the communication module 110, thereby increasing user convenience. It may be.

Hereinafter, a configuration in which the common message distributor 120 receives or intercepts a window message from the first module 201 and transmits the window message to the second module 202 will be described with reference to FIG. 2.

2 is a detailed internal view of a common message distributor according to an embodiment of the present invention.

In the embodiment of FIG. 2, it is assumed that the common message distributor 200 receives a window message from the first module 201 and transmits the window message to the second module 202.

As shown in FIG. 2, the common message distributor 200 may include a communication unit 210, a storage unit 220, and a control unit 230.

The communication unit 210 may receive or intercept a window message from the module 201. The communicator 210 may store the received window message in the storage 220.

In addition, the communication unit 210 may transmit the window message to the module 202 determined as a transmission destination according to the window message transmission path determined by the control unit 230.

The storage unit 220 may store the window message received from the communication unit 210. In addition, the storage unit 220 may register and store a window handle of a dynamic link library (DLL) module periodically or aperiodically. Here, the DLL may include a callback function, a header information interpretation function, a window handle initialization function, a transfer function, and the like that may be used to analyze a window message to determine a message transmission path.

The controller 230 may include an event detector 231, a callback function caller 232, a window message extractor 233, a header information parser function caller 234, and a header information parser 235.

The event detector 231 may detect whether the communication unit 210 has received a window message from the first module 201. When the window message is received from the first module 210, the communication unit 210 may transmit the same to the storage unit 220 as described above, and at the same time, the event message unit 231. The configuration that the communication unit 210 transmits to both components of the storage unit 220 and the event detection unit 231 can be easily derived by those skilled in the art, and a detailed description thereof will be omitted.

Alternatively, the communication unit 210 may further include a preset clock signal generation circuit. The communication unit 210 generates a preset clock signal by triggering the reception of a window message from the first module 210. The event detector 231 may transmit the data. The event detector 231 may determine that the predetermined clock signal is received as an event. In addition to the above-described method, the event detector 231 may implement event detection in various ways.

When the event detector 231 detects the event that the communication unit 210 has received the window message through the above-described configuration, the event detector 231 transmits a command message for calling the callback function to the callback function caller 232. Can be.

When the command message to call the callback function is received from the event detector 231, the callback function caller may call the callback function from the storage 220. Here, the callback function is a target of a callback that designates an application function called by an operating system (OS), and may be designated to be called when a specific event or message occurs. The event in this embodiment may be that the event detector 231 receives a notification that the communication unit 210 has received a window message.

On the other hand, the callback function can use a queue as a data structure, and thus the callback function can process the queue in a FIFO (first in first out) manner. That is, the controller 230 according to the present embodiment may process window messages one by one in the queue of the callback function.

The window message extractor 233 may extract a window message stored in the storage 220 in response to the callback function being called. As described above, since the window message is processed in the FIFO method, the window message extractor 233 may also extract the window messages one by one.

Meanwhile, the window message extractor 233 may further include a medium capable of storing the window message. For example, the window message extractor 233 may include a shift register. Thus, the window message extractor 233 may include a shift register. The window message may be extracted and output to the header information analyzer 235.

The process of extracting the window message by the window message extractor 233 by the FIFO method is illustrated in FIG. 3. 3 is a conceptual diagram conceptually illustrating a queue of a callback function. As shown in FIG. 3, the arrow direction of FIG. 3 is lapsed with time. As shown in FIG. 3, it can be seen that the queue of the callback function is stored in the order of the first queue, the third queue, and the second queue in the first step. . Here, the first queue, the second queue, and the third queue may be window messages received from each module and stored in the storage unit 220. The storage order of the first queue-third queue-second queue may preferably be a time-series order received by the communication unit 210. However, when a queue is received at time intervals that cannot be distinguished in time series, a plurality of queues may be stored in a predetermined rank.

The window message extractor 233 may output the first queue to the header information analyzer 235 and store the fifth queue as a new queue. In the second step illustrated in FIG. 3, it can be seen that the callback function is stored in the queue of the third queue, the second queue, and the fifth queue.

The window message extractor 233 may output the third queue to the header information analyzer 235 and store the fourth queue as a new queue. In the third step illustrated in FIG. 3, it may be confirmed that the callback function is stored in the queue of the second queue, the fifth queue, and the fourth queue. Meanwhile, although the queue of the callback function is illustrated as a linear queue in FIG. 3, those skilled in the art can easily design a linear queue into an annular queue.

As described above, as the callback function uses the queue as a data structure, the callback function may output window messages to the header information analyzer 235 one by one.

The window message extractor 233 may extract the window message from the storage 220 and transmit a notification message indicating that the window message has been extracted to the header information analysis function caller 234.

The header information function caller 234 may call the header information interpretation function from the storage unit 220 by using the notification message received from the window message extraction unit 233 as a trigger, and the header information interpretation function is called as a header. The data may be output to the information analyzer 235.

The header information analyzer 235 may interpret the header information of the window message by using the window message received from the window message extractor 233 and the header information interpreter received from the header information interpreter caller 234. .

The window message may include a transmission destination as a first factor, a message type as a second factor, and message content as a third factor.

The following description is an example of a function describing a window message.

LRESULT SendMessageTimeout (

HWND hWnd, // handleto window

UINT Msg, // message

WPARAM wParam, // first message parameter

LPARAM lParam, // second message parameter

UINT fuFlages, // send options

UINT uTimeout, // time-out duration

PDWORD_PTR lpdwResult // return value for synchronous call

);

The header information interpreting unit 235 may determine the transmission destination of the window message by interpreting each factor included in the window message, and simultaneously communicates the window message and the transmission destination, for example, information of the second module 202 with the communication unit 210. ) Can be sent. The communication unit 210 may transmit the window message to the second module 202 using the received transmission destination.

According to the above-described configuration, the common message distributor drives both callback functions of the first module 201 and the second module 202 to receive all the window messages transmitted from the first module 201 and the second module 202. Alternatively, you can intercept and interpret the transmission destination contained in the window message. Accordingly, even in a situation where a window message is received from a plurality of modules, the common message distributor 200 may process the window message in a FIFO manner in the queue of the callback function and stably transmit the window message to the transmission destination.

Hereinafter, a window message transmission method of a common message distributor according to another aspect of the present invention will be described with reference to FIG. 4.

4 is a flowchart illustrating a window message transmission method of a common message distributor according to an embodiment of the present invention.

First, the window handle of the DLL module may be registered in the common message distributor (S410). Since the above DLL has been described above with reference to FIG. 1, a detailed description of the DLL will be omitted here.

The window handle of the DLL module is registered, and the common message distributor may detect an event that the window message has been received (S420). When the common message distributor detects the window message receiving event, the callback function may be called (S430), and the window message may be processed by the FIFO method as described above in the queue of the called callback function.

When the window message is stored in the queue of the callback function, the common message distributor may call the header information interpretation function and analyze the window message by using the called header information interpretation function (S440).

In addition, the common message distributor may determine the transmission destination and the transmission path according to the window message analysis result (S450), and transmit the window message to the determined transmission destination (S460).

According to the window message transmission method described above, even in a situation where a window message is received from a plurality of modules, the common message distributor can stably transmit the window message to the transmission destination by processing the window message in the FIFO method in the queue of the callback function.

200: common message distributor 210: communication unit
220: storage unit 230: control unit
231: event detection unit 232: call ball function call unit
233: window message extraction unit 234: header information interpretation function call unit
235: header information analysis unit

Claims (7)

In the window message transmission method of the common message distributor connected to at least one module,
Registering a window handle of a dynamic link library (DLL) module including a callback function for storing the window message in a queue and a header information interpretation function for interpreting the window message;
Detecting an event receiving the window message from the at least one module,
If the event is detected, calling the callback function and storing the window message in a queue of the callback function;
Invoking the header information parsing function, analyzing the window message stored in the queue of the callback function;
Determining a transmission path of the window message using the analysis result of the window message;
Transmitting the window message along the transmission path;
And the window message sets a transmission path of the window message as a first parameter, a type of the window message as a second parameter, and contents of the window message as a third parameter. delete The method of claim 1,
The function that describes the window message is
LRESULT SendMessageTimeout (
HWND hWnd, // handleto window
UINT Msg, // message
WPARAM wParam, // first message parameter
LPARAM lParam, // second message parameter
UINT fuFlages, // send options
UINT uTimeout, // time-out duration
PDWORD_PTR lpdwResult // return value for synchronous call
);
Window message transmission method, characterized in that. In the common message distributor that is connected to a plurality of modules, and transmits a window message,
Communication unit for receiving a window message from the plurality of modules,
A storage unit for storing a window handle of a dynamic link library (DLL) module including the window message, a callback function for storing the window message in a queue, and a header information interpretation function for interpreting the window message;
A control unit configured to determine a transmission destination of the window message by using the callback function and the header information interpretation function called from the storage unit, and to control the communication unit to transmit the window message to the determined transmission destination;
And wherein the window message sets a transmission path of the window message as a first parameter, a type of the window message as a second parameter, and contents of the window message as a third parameter. delete The method of claim 4, wherein
The function that describes the window message is
LRESULT SendMessageTimeout (
HWND hWnd, // handleto window
UINT Msg, // message
WPARAM wParam, // first message parameter
LPARAM lParam, // second message parameter
UINT fuFlages, // send options
UINT uTimeout, // time-out duration
PDWORD_PTR lpdwResult // return value for synchronous call
);
A common message distributor. The method of claim 4, wherein
The control unit,
An event detector for detecting an event in which the communication unit receives the window message;
A callback function caller which calls the callback function from the storage when the event detector detects the event;
A window message extracting unit extracting the window message from the storage unit;
A header information analysis function call unit for calling the header information analysis function from the storage unit;
A header information analyzer configured to analyze the window message by using the window message received from the window message extractor and the header information interpreter received from the header information interpreter caller, and determine a transmission destination of the window message. Including common message distributor.

Images