Geek asks and answers

Simple chat protocol

I study networks and flows in C #. To do this, I am developing a chat via the network.

I currently have a basic client-server communication (TCP). The server can work with several clients. But only client-server communication. Basically, the client sends an ASCII encoded message to the server, then the server decodes it and displays it in the console.

Currently, I want to implement Client-Client communication.

Suppose we have an online list of clients in each client and a message box to send a message to each client.

The next step is the click button, which will compose the Socket and send, then the server should understand who the message is addressed to.

So, what should be my message structure and how should I understand in Server who the message is addressed to?

I don’t need the code at all, I want a theory. Simple and short. Maybe textbooks?

I looked into XMPP. It's very hard. I just need guidance on how I can do this. My goal is to learn, not to realize and forget.

0
source share
1 answer

TCP is flow-based, which means you'll never know, using TCP, when a message starts and ends. Any message / protocol design should solve this.

There are two ways to determine when a message ends. The first way is to add a separator at the end of the message, and the second way is to include the length in the header.

HTTP . , , . Content-Length, , .

, (4 ) - , - . , ( ).

, . , , ( , ). , , . /, ​​ HTTP ( , X- ).

:

From: Arne
To: #ChannelName
WrittenAt: 2011-07-03 12:00 GMT
Content-Length: 16

This is a text

, 16, , .

-, , . , , ( ).

To, .

+5

More articles:


All Articles