C#为什么 "Flush"不能将字节强制向下传输到网络流中？

我有一个项目，试图将序列化的对象发送到服务器，然后等待“确定”或“错误”消息返回。
我似乎与TcpClient send/close problem的发布者有类似的问题
问题是，我似乎能够发送原始对象的唯一方法是关闭连接，但是(当然)我迫不及待地想看看服务器是否成功处理了该对象。

private void button4_Click(object sender, EventArgs e)
{
    RequestPacket req = new RequestPacket();

    /// ... Fill out request packet ...

    /// Connect to the SERVER to send the message...
    TcpClient Client = new TcpClient("localhost", 10287);
    using (NetworkStream ns = Client.GetStream())
    {
        XmlSerializer xml = new XmlSerializer(typeof(RequestPacket));
        xml.Serialize(ns, req);

        /// NOTE: This doesn't seem to do anything....
        ///       The server doesn't get the object I just serialized.
        ///       However, if I use ns.Close() it does...
        ///          but then I can't get the response.
        ns.Flush();

        // Get the response. It should be "OK".
        ResponsePacket resp;

        XmlSerializer xml2 = new XmlSerializer(typeof(ResponsePacket));
        resp = (ResponsePacket)xml2.Deserialize(ns);


        /// ... EVALUATE RESPONSE ...
    }

    Client.Close()
}

更新:作为对一位评论者的回应，我认为客户可能不会有过错。它只是在等待对象，并且直到我关闭套接字时对象才会出现..但是，如果我错了，我会很高兴公开吃乌鸦。 =)这是客户:

    static void Main(string[] args)
    {
        // Read the port from the command line, use 10287 for default
        CMD cmd = new CMD(args);
        int port = 10287;

        if (cmd.ContainsKey("p")) port = Convert.ToInt32(cmd["p"]);

        TcpListener l = new TcpListener(port);
        l.Start();

        while (true)
        {
            // Wait for a socket connection.
            TcpClient c = l.AcceptTcpClient();

            Thread T = new Thread(ProcessSocket);

            T.Start(c);
        }
    }


    static void ProcessSocket(object c)
    {
        TcpClient C = (TcpClient)c;

        try
        {
            RequestPacket rp;
            //// Handle the request here.
            using (NetworkStream ns = C.GetStream())
            {
                XmlSerializer xml = new XmlSerializer(typeof(RequestPacket));
                rp = (RequestPacket)xml.Deserialize(ns);
            }

            ProcessPacket(rp);
        }
        catch
        {
            // not much to do except ignore it and go on.
        }
    }

是的...就是这么简单。

最佳答案

嗯，你可以怪Nagle's algorithm。但是，它与C#无关，这是TCP/IP堆栈的默认行为。使用NoDelay方法启用SetSocketOption套接字选项。但是要小心，禁用Nagle的算法会降低吞吐量。

我也不确定您是在套接字顶部使用的流，因为我根本不是C#开发人员，但请尝试删除其实例，以确保它确实可以编写:-)