KR980010828A - How to send messages - Google Patents

Abstract

The present invention provides a system for enabling a recipient to immediately know that a message has been received upon receipt of a message, reading the received message, and then reading the message from the recipient to the sender, In order to solve the above problems, there is provided a method for transmitting a message in a message transmission / reception system of a client and a server environment, comprising the steps of: waiting for a response from a receiver for a predetermined period of time; A step in which the system daemon activates the mail system when receiving a message on the receiving side and a step in which the activated mail system displays the received message on the screen To alert the recipient while And a step in which the receiver generates and transmits a response message.

Description

How to send messages

Accordingly, it is an object of the present invention to provide a system for enabling a recipient to immediately know that a message has been received upon receipt of a message, reading the received message, The purpose.

Means for solving the problem

In order to solve the above-described problems, the present invention provides a method for transmitting a message in a message transmission / reception system of a client and a server environment, the method comprising the steps of: waiting for a response from a receiver for a predetermined period of time; A step in which the system daemon activates the mail system upon receipt of a message at the reception side, and a step in which the activated mail system displays the received message on the screen A step of transmitting an alarm to the receiver while displaying the message, and a step of creating and transmitting a response message by the receiver.

Also, more specifically, alerts sent to the recipient may cause the screen to flicker or change certain icons on the screen.

Example

Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

FIG. 1 is a diagram showing an embodiment of the present invention in which SUPERMP is a client and INET1, INT2,... Are servers. Software (Tmail) for implementing the present invention is installed in the client and software (tmailser) is installed in the server side. The server-side tmailser is not always loaded on the server's memory, but it is driven by inetd, the system daemon when messages are received.

Clients and servers can be connected by LAN (Local Area Network) or by other dedicated lines and communication lines. It is needless to say that the client and the server have to be equipped with communication equipment corresponding to the communication line, respectively.

The Tmail and Tmailser programs are implemented as X / Motif GUI (Graphic User Interface), respectively, and provide convenience to users. That is, the user ID and the system ID of the other party to be sent are set as icons in advance, and the message is transmitted by clicking the mouse. That is, as shown in FIG. 2, the user ID and the system ID address of each server are displayed as icons, and the user can click the mouse to easily send the message to one or a plurality of servers. At the same time, messages from multiple servers can be simultaneously received and displayed on the screen. This is the initial screen of Tmail in this embodiment of FIG. 2. A message sent in the transmission process can be created by starting an editor in the menu of Tmail (third view), and the pre-written message can be sent in a file form (FIG. 4).

The communication method of this embodiment will be described below with reference to FIG. 5.

First, a message is created (S1). This message can be created by activating the editor in the transmission process so that the message can be prepared in advance and stored in the form of a file and then sent. Click on the icon of the person you want to send the message to, and then click on the icon to send the message. In this case, it is needless to say that the message can be transmitted by directly inputting the user ID and the system ID address of the other party to which the message is to be sent, from the keyboard or the like. The client sending the message in S3 sets a fixed time and waits for a response. If there is no response until this time has elapsed, it is considered a transmission failure and another transmission method is considered. If a response message is received within this time (S4), it is displayed on the screen (S5). On the other hand, when the server receives the message (R1), the mailser is activated to generate an alarm (R2) and display the received message on the screen (see FIG. This alarm will make the sound louder, blink the screen, or change the specific icon so that the receiver can recognize it immediately. (R4) and transmits the response message to the client side (R5). Unlike the above embodiment, even when a server generates and transmits a dust message, The same message is transmitted and received.

Figure 1 illustrates a client / server configuration that is an environment of the present invention.

FIG. 2 is an initial screen of message transmission on the client side; FIG.

3 is a transmission message preparation screen on the transmission side.

FIG. 4 is a screen for transmitting a file created in advance on the transmitting side.

FIG. 5 is a flow chart showing a communication method of the present invention. FIG.

FIG. 6 is a diagram showing a reception message on the reception side displayed on the screen.

Commercial use field

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a method of transmitting and receiving a message using a computer, and more particularly, to a method of transmitting a message useful for a system such as network management,

Conventional technology and its problems

Previously, there were mail systems provided by UNIX or X Windows. However, these mail systems have the following problems. First, a mail daemon always exists in the system in order to receive messages, resulting in loss of system support. Also, the sender of the message can not know that the recipient has read the message, other than that the message has been delivered. Third, even if the recipient sends a response message, the sender can not know immediately. Fourth, the method of notifying the receipt of the message ("beep" sound or ICON appearance change) is too weak, so even if it is an urgent message, the receiver can not detect it and can pass it.

Under such a system, if you can send mail but you need to get a reply or not, but you want to confirm that the other party has received it, there is no special way to do so without using a telephone or other means.

As described above, since the program on the server side is not always loaded into the memory, but the system is activated by the system daemon every time a message is received, the load on the system is reduced.

Also, since the GUI is used, the user ID and system ID of the server can be sent and received simply and conveniently by converting the address into an icon.

Also, by receiving the message and prompting it to respond immediately, the sender can immediately know the reception status.

Claims (3)

A system for transmitting and receiving messages in a client and server environment, the system comprising: sending a message and waiting for a response from a receiver for a predetermined period of time; displaying a response on the monitor screen when a response is received within a predetermined period of time; A step in which the system daemon activates the mail system upon receipt of a message at the receiving end, and a step in which the activated mail system displays an alert to the recipient while displaying the received message on the screen, And a step of the recipient creating and transmitting a response message. And an alert sent to the recipient causes the screen to blink. The method of claim 1, wherein the alert sent to the recipient alters a specific icon on the screen. ※ Note: It is disclosed by the contents of the first application.