Win32 API用于服务器-客户端管道通信的顺序是什么在C ++中CreateNamedPipe,WriteFile,CreateFile,ReadFile

如何解决Win32 API用于服务器-客户端管道通信的顺序是什么在C ++中CreateNamedPipe,WriteFile,CreateFile,ReadFile

我试图使用Win32 API在Visual Studio 2019中用C ++编写服务器/客户端程序。

这是相关文档:Named Pipe Open Modes

我使用了4个API:

在服务器端(创建管道并对其进行写操作的一方):CreateNamedPipe()WriteFile()

在客户端(通过管道进行连接和读取):CreateFile()ReadFile()

但是,我发现服务器无法写入管道。

以下是我使用的代码。

Servermain.cpp

#include <iostream>
#include <windows.h>

using namespace std;

void namedPipeServer()
{
    HANDLE hPipeServer;
    char Wbuffer[1024] = "Hello,from the pipe server!";
    DWORD dwWrite;
    BOOL writeSuccessFlag;

    //Create a named pipe
    hPipeServer = CreateNamedPipe(
        TEXT("\\\\.\\pipe\\Agentpipe"),//lpName
        PIPE_ACCESS_OUTBOUND,//dwOpenMode
        PIPE_TYPE_BYTE,//dwPipeMode
        1,//nMaxInstances
        1024 * 16,//nOutBufferSize
        1024 * 16,//nInBufferSize
        NMPWAIT_USE_DEFAULT_WAIT,//nDefaultTimeOut
        NULL);                     //lpSecurityAttributes

    cout << "Inside namedPipeServer()" << endl;

    if (hPipeServer != INVALID_HANDLE_VALUE)
    {
        cout << "Just writing to pipe" << endl;

        writeSuccessFlag = WriteFile(
            hPipeServer,//HANDLE       hFile
            Wbuffer,//LPCVOID      lpBuffer
            30,//DWORD        nNumberOfBytesToWrite
            &dwWrite,NULL         //LPOVERLAPPED lpOverlapped
        );

        if (writeSuccessFlag)
        {
            cout << "Server has written to pipe!" << endl;
        }
        else
        {
            cout << "Unsuccessful write to pipe,From Agent" << endl;
        }
    }
    else
    {
        cout << "Unsuccesful pipe connection. hPipeServer: " << hPipeServer << endl;
    }
}

int main()
{
    cout << "Inside Agent server. Creating a named pipe.\n" << endl;
    namedPipeServer();
    while (1);
    return 0;
}

Clientmain.cpp:

#include <iostream>
#include <windows.h>

using namespace std;

void readFromPipe()
{
    HANDLE hPipeClient;
    char rBuffer[1024];
    DWORD dwRead;
    BOOL readSuccessFlag = 0;

    //Connect to the server pipe: \\.\\pipe\\Agentpipe
    cout << "Inside readFromPipe()." << endl;

    hPipeClient = CreateFile(
        TEXT("\\\\.\\pipe\\Agentpipe"),//lpFileName
        GENERIC_READ,FILE_SHARE_READ,NULL,OPEN_EXISTING,NULL
    );

    while (hPipeClient != INVALID_HANDLE_VALUE)
    {
        cout << "Just connecting to pipe" << endl;
        readSuccessFlag = ReadFile(
            hPipeClient,//HANDLE       hFile,rBuffer,//LPVOID       lpBuffer,30,//DWORD        nNumberOfBytesToRead,&dwRead,//LPDWORD      lpNumberOfBytesRead,NULL         //LPOVERLAPPED lpOverlapped
        );

        if (readSuccessFlag)
        {
            cout << "Client has read from pipe of Agent!" << endl;
            cout << "From Agent Pipe: " << rBuffer << endl;
        }
        else
        {
            cout << "Unsuccessful Pipe read!" << endl;
        }
    }
    if(hPipeClient == INVALID_HANDLE_VALUE)
    {
        cout << "Unsuccesful pipe connection at client end. hPipeClient: " << hPipeClient << endl;
    }
}

int main()
{
    cout << "Inside the client. Calling readFromPipe()" << endl;
    readFromPipe();
    while (1);
    return 0;
}

执行上述程序后,表明服务器无法写入管道,并且服务器端的输出为:

Inside Agent server. Creating a named pipe.
Inside namedPipeServer()
Just writing to pipe
Unsuccessful write to pipe,From Agent

客户端控制台上的输出为:

Inside the client. Calling readFromPipe()
Inside readFromPipe().
Just connecting to pipe

在查看Win32文档中的示例程序时,我发现这些Win32 API的使用顺序不同,如下所示:

Pipe Server程序:

main(){
    ...
    namedPipeServer()
    ...
}

void namedPipeServer()
{
    ...
    CreateFile()
    WriteFile()
    ...
}

Pipe Client程序:

main(){
    ...
    readFromPipe()
    ...
}

void readFromPipe()
{
    ...
    CreateNamedPipe()
    ReadFile()
    ...
}

如果有人可以特别明确地说明我对CreateNamedPipe()CreateFile()的使用,我将感到高兴。

服务器是否必须首先使用CreateFile()(在创建管道之前,先将其写入),还是可以使用CreateNamedPipe()

MY 程序中使用API​​的顺序发布不正确吗?如果是这样,请说明原因。

版权声明:本文内容由互联网用户自发贡献,该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容, 请发送邮件至 dio@foxmail.com 举报,一经查实,本站将立刻删除。

相关推荐


使用本地python环境可以成功执行 import pandas as pd import matplotlib.pyplot as plt # 设置字体 plt.rcParams[&#39;font.sans-serif&#39;] = [&#39;SimHei&#39;] # 能正确显示负号 p
错误1:Request method ‘DELETE‘ not supported 错误还原:controller层有一个接口,访问该接口时报错:Request method ‘DELETE‘ not supported 错误原因:没有接收到前端传入的参数,修改为如下 参考 错误2:cannot r
错误1:启动docker镜像时报错:Error response from daemon: driver failed programming external connectivity on endpoint quirky_allen 解决方法:重启docker -&gt; systemctl r
错误1:private field ‘xxx‘ is never assigned 按Altʾnter快捷键,选择第2项 参考:https://blog.csdn.net/shi_hong_fei_hei/article/details/88814070 错误2:启动时报错,不能找到主启动类 #
报错如下,通过源不能下载,最后警告pip需升级版本 Requirement already satisfied: pip in c:\users\ychen\appdata\local\programs\python\python310\lib\site-packages (22.0.4) Coll
错误1:maven打包报错 错误还原:使用maven打包项目时报错如下 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-resources-plugin:3.2.0:resources (default-resources)
错误1:服务调用时报错 服务消费者模块assess通过openFeign调用服务提供者模块hires 如下为服务提供者模块hires的控制层接口 @RestController @RequestMapping(&quot;/hires&quot;) public class FeignControl
错误1:运行项目后报如下错误 解决方案 报错2:Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project sb 解决方案:在pom.
参考 错误原因 过滤器或拦截器在生效时,redisTemplate还没有注入 解决方案:在注入容器时就生效 @Component //项目运行时就注入Spring容器 public class RedisBean { @Resource private RedisTemplate&lt;String
使用vite构建项目报错 C:\Users\ychen\work&gt;npm init @vitejs/app @vitejs/create-app is deprecated, use npm init vite instead C:\Users\ychen\AppData\Local\npm-
参考1 参考2 解决方案 # 点击安装源 协议选择 http:// 路径填写 mirrors.aliyun.com/centos/8.3.2011/BaseOS/x86_64/os URL类型 软件库URL 其他路径 # 版本 7 mirrors.aliyun.com/centos/7/os/x86
报错1 [root@slave1 data_mocker]# kafka-console-consumer.sh --bootstrap-server slave1:9092 --topic topic_db [2023-12-19 18:31:12,770] WARN [Consumer clie
错误1 # 重写数据 hive (edu)&gt; insert overwrite table dwd_trade_cart_add_inc &gt; select data.id, &gt; data.user_id, &gt; data.course_id, &gt; date_format(
错误1 hive (edu)&gt; insert into huanhuan values(1,&#39;haoge&#39;); Query ID = root_20240110071417_fe1517ad-3607-41f4-bdcf-d00b98ac443e Total jobs = 1
报错1:执行到如下就不执行了,没有显示Successfully registered new MBean. [root@slave1 bin]# /usr/local/software/flume-1.9.0/bin/flume-ng agent -n a1 -c /usr/local/softwa
虚拟及没有启动任何服务器查看jps会显示jps,如果没有显示任何东西 [root@slave2 ~]# jps 9647 Jps 解决方案 # 进入/tmp查看 [root@slave1 dfs]# cd /tmp [root@slave1 tmp]# ll 总用量 48 drwxr-xr-x. 2
报错1 hive&gt; show databases; OK Failed with exception java.io.IOException:java.lang.RuntimeException: Error in configuring object Time taken: 0.474 se
报错1 [root@localhost ~]# vim -bash: vim: 未找到命令 安装vim yum -y install vim* # 查看是否安装成功 [root@hadoop01 hadoop]# rpm -qa |grep vim vim-X11-7.4.629-8.el7_9.x
修改hadoop配置 vi /usr/local/software/hadoop-2.9.2/etc/hadoop/yarn-site.xml # 添加如下 &lt;configuration&gt; &lt;property&gt; &lt;name&gt;yarn.nodemanager.res