【问题标题】:linux socket lose data when a delay is added before read在读取之前添加延迟时,linux套接字丢失数据
【发布时间】:2020-09-14 15:00:27
【问题描述】:

我正在学习linux套接字编程,我希望服务器可以读取数据,即使我添加了延迟但它只是丢弃缓冲区数据,并接收最近的数据,这就是为什么,谢谢。代码已提交。 顺便问一下,您能介绍一下处理这种情况的常用做法吗?

服务器端C/C++程序演示Socket编程

#include <unistd.h>
#include <stdio.h>
#include <sys/socket.h>
#include <stdlib.h>
#include <netinet/in.h>
#include <string.h>
#define PORT 8080
int main(int argc, char const *argv[])
{
    int server_fd, new_socket, valread;
    struct sockaddr_in address;
    int opt = 1;
    int addrlen = sizeof(address);
    char buffer[1024] = {0};
    const char hello[] = "Hello from server";

    // Creating socket file descriptor
    if ((server_fd = socket(AF_INET, SOCK_STREAM, 0)) == 0)
    {
        perror("socket failed");
        exit(EXIT_FAILURE);
    }

    // Forcefully attaching socket to the port 8080
    if (setsockopt(server_fd, SOL_SOCKET, SO_REUSEADDR | SO_REUSEPORT,
                   &opt, sizeof(opt)))
    {
        perror("setsockopt");
        exit(EXIT_FAILURE);
    }
    address.sin_family = AF_INET;
    address.sin_addr.s_addr = INADDR_ANY;
    address.sin_port = htons(PORT);

    // Forcefully attaching socket to the port 8080
    if (bind(server_fd, (struct sockaddr *)&address,
             sizeof(address)) < 0)
    {
        perror("bind failed");
        exit(EXIT_FAILURE);
    }
    if (listen(server_fd, 3) < 0)
    {
        perror("listen");
        exit(EXIT_FAILURE);
    }
    if ((new_socket = accept(server_fd, (struct sockaddr *)&address,
                             (socklen_t *)&addrlen)) < 0)
    {
        perror("accept");
        exit(EXIT_FAILURE);
    }
    for (int i = 0;; i++)
    {
        sleep(5);
        valread = read(new_socket, buffer, 1024);
        printf("%s\n", buffer);
    }
    send(new_socket, hello, strlen(hello), 0);
    printf("Hello message sent\n");
    return 0;
}

客户端C/C++程序演示Socket编程

#include <stdio.h>
#include <sys/socket.h>
#include <arpa/inet.h>
#include <unistd.h>
#include <string>
#include <string.h>
#define PORT 8080

int main(int argc, char const *argv[])
{
    int sock = 0, valread;
    struct sockaddr_in serv_addr;
    const char data[] = "Hello from client";
    char buffer[1024] = {0};
    if ((sock = socket(AF_INET, SOCK_STREAM, 0)) < 0)
    {
        printf("\n Socket creation error \n");
        return -1;
    }

    serv_addr.sin_family = AF_INET;
    serv_addr.sin_port = htons(PORT);

    // Convert IPv4 and IPv6 addresses from text to binary form
    if (inet_pton(AF_INET, "127.0.0.1", &serv_addr.sin_addr) <= 0)
    {
        printf("\nInvalid address/ Address not supported \n");
        return -1;
    }

    if (connect(sock, (struct sockaddr *)&serv_addr, sizeof(serv_addr)) < 0)
    {
        printf("\nConnection Failed \n");
        return -1;
    }
    for (int i = 0;; i++)
    {
        sleep(1);
        std::string hello = std::string(data) + std::to_string(i);
        if (send(sock, hello.c_str(), hello.length() + 1, 0) != hello.length() + 1)
        {
            printf("error send %d \n", i);
        }
        printf("Hello message sent %d\n", i);
    }
    valread = read(sock, buffer, 1024);
    printf("%s\n", buffer);
    return 0;
}

【问题讨论】:

  • TCP 是一种流式协议 - 您不能假设 buffer 的内容是零终止的,并且 read 不会与 send“匹配”。您还需要检查valread 是否成功。
  • 客户端和服务器都不会通过for (int i = 0; ; i++) 循环 - 这是有意的吗?
  • 睡眠的目的是什么? recv 已经等到有数据了。
  • 好像丢了奇怪的数据,请问服务器丢失的数据怎么弄?
  • 考虑来自客户端的以下流:"Hello from Client0\0Hello from Client1\0Hello from Client2\0..." 如果您在每个recv 中收到 30 个字节,您首先会看到“Hello from Client0”(因为您是 printfing) ,对于第二个recv,您将看到“Client1”。

标签: c++ c linux sockets


【解决方案1】:

您阻止服务器 5 秒钟,它无法接收来自客户端的某些消息。

    for (int i = 0;; i++)
    {
        sleep(5);
        valread = read(new_socket, buffer, 1024);
        printf("%s\n", buffer);
    }

客户端如何检查服务器是否正在接收消息?我想这在Linux socket: How to make send() wait for recv()

中讨论过

附:看起来有一段同步代码,但你把它从循环中拉了出来。

服务器:

}
send(new_socket, hello, strlen(hello), 0);

客户:

}
valread = read(sock, buffer, 1024);

【讨论】:

    猜你喜欢
    • 2013-06-21
    • 1970-01-01
    • 2020-02-07
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 2020-02-07
    相关资源
    最近更新 更多