https://github.com/manfredipist/qtcpsocket
A simple Qt client-server TCP architecture to transfer data between peers
https://github.com/manfredipist/qtcpsocket
cplusplus peers qt5 qtcpsocket tcp tcp-client tcp-server tcp-socket transfer-messages
Last synced: about 1 year ago
JSON representation
A simple Qt client-server TCP architecture to transfer data between peers
- Host: GitHub
- URL: https://github.com/manfredipist/qtcpsocket
- Owner: manfredipist
- License: gpl-3.0
- Created: 2018-11-15T20:50:22.000Z (over 7 years ago)
- Default Branch: master
- Last Pushed: 2022-04-28T14:14:09.000Z (about 4 years ago)
- Last Synced: 2025-03-31T22:27:13.694Z (about 1 year ago)
- Topics: cplusplus, peers, qt5, qtcpsocket, tcp, tcp-client, tcp-server, tcp-socket, transfer-messages
- Language: C++
- Homepage:
- Size: 594 KB
- Stars: 135
- Watchers: 3
- Forks: 41
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# QTcpSocket
A simple Qt client-server TCP architecture to transfer data between peers.
The Architecture is made up of 2 projects:
- QTCPServer
- QTCPClient
You can instantiate as many QTCPClient as you wish.
## Features
1. Broadcast transferring
2. Single channel transferring
3. Media transferring capabilities (*.json, *.txt, *.png, *.jpg, *.jpeg)
4. Updated to latest slot-signal syntax found in Qt 5.15
5. Non-redundant design
## Protocol
The protocol i've designed to enable data transferring is pretty straightforward, each message sent is made up of:
- A 128 byte fixed-size header
- A Non-fixed size data buffer
The header follows the following structure:
```
QString header = QString("fileType:%1, fileName:%2, fileSize:%3;")
```
Where:
- ```%1``` can be "attachment" or "message";
- ```%2``` is "null" for messages, the correspondent fileName for attachments sent;
- ```%3``` is the size of the message or the attachment sent.
Many improvements could have been made during protocol design, one among many, to specify header size in the header and save up some byte during transfers, especially messages ones.
__*This protocol is meant to be used only for recreative purposes as it isn't compliant at all to the FTP quality standards, that we are used to, nowadays.*__