https://github.com/deruina/minitalk

Minitalk Client-Server Communication This repository contains a lightweight client-server application implemented in C, using the Minitalk protocol for efficient and reliable communication. The project includes separate source code files for the client and server, and utilizes a custom library, libft.
https://github.com/deruina/minitalk

42 42projects minitalk

Last synced: 2 months ago
JSON representation

Minitalk Client-Server Communication This repository contains a lightweight client-server application implemented in C, using the Minitalk protocol for efficient and reliable communication. The project includes separate source code files for the client and server, and utilizes a custom library, libft.

• Host: GitHub
• URL: https://github.com/deruina/minitalk
• Owner: DeRuina
• Created: 2023-01-11T13:13:42.000Z (over 2 years ago)
• Default Branch: master
• Last Pushed: 2023-02-02T09:08:53.000Z (over 2 years ago)
• Last Synced: 2025-01-18T07:47:14.490Z (4 months ago)
• Topics: 42, 42projects, minitalk
• Language: C
• Homepage:
• Size: 264 KB
• Stars: 0
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# minitalk

- This project creates two executables: server & client.

- The client will send information (a string) to the server using UNIX signals and then will dispaly a message after the information has reached the server.

- The server must correctly receive and interpret this information, display it and then send a signal back that acknowledges the recieved information.

- The Makefile compiles both the server and the client as executables.

```bash

 make

```

### Behaviour:

1) By running the server executable we start up the server and it displays a message and its process id: 

![server start](img/1.png)

2) By running the client executable with the server's process id as a first argument we can add any string we want as a second argument: 

![client start](img/2.png)

3) The server receives signals which are translated to bits which are then translated to characters. The server prints the result as a string: 

![server print](img/3.png)

4) The server sends a signal back to the client which approves the string was recieved. The client then prints a message:

![client print](img/4.png)

#### Additional behaviour:

1) The client can also send Unicode format characters:

![unicode](img/5.png)

2) The server interprets and displays them correctly:

![print unicode](img/6.png)

3) The server can recieve signals from multiple clients without needing to restart:

![mutiple clients](img/6.png)

### Evaluated by 42 

![125/100](img/125.png)

## Author

- [@DeRuina](https://github.com/DeRuina)