我正在尝试实现一个解决方案,在该解决方案中,服务会为多个 Worker 安排一些工作。调度本身应该通过自定义的基于 tcp 的协议(protocol)进行,因为 Worker 可以在同一台机器或不同的机器上运行。
经过一些研究,我找到了 this邮政。阅读之后,我发现至少有 3 种不同的可能解决方案,每种都有其优点和缺点。
我决定采用 Begin-End 解决方案,并编写了一个小测试程序来试用它。 我的客户端只是一个简单的程序,它向服务器发送一些数据然后退出。 这是客户端代码:
class Client
{
static void Main(string[] args)
{
var ep = new IPEndPoint(IPAddress.Parse("127.0.0.1"), 12345);
var s = new Socket(ep.AddressFamily, SocketType.Stream, ProtocolType.Tcp);
s.Connect(ep);
Console.WriteLine("client Startet, socket connected");
s.Send(Encoding.ASCII.GetBytes("1234"));
s.Send(Encoding.ASCII.GetBytes("ABCDEFGH"));
s.Send(Encoding.ASCII.GetBytes("A1B2C3D4E5F6"));
Console.ReadKey();
s.Close();
}
}
按照提供的示例,我的服务器几乎一样简单:
class Program
{
static void Main(string[] args)
{
var server = new BeginEndTcpServer(8, 1, new IPEndPoint(IPAddress.Parse("127.0.0.1"), 12345));
// var server = new ThreadedTcpServer(8, new IPEndPoint(IPAddress.Parse("127.0.0.1"), 12345));
//server.ClientConnected += new EventHandler<ClientConnectedEventArgs>(server_ClientConnected);
server.DataReceived += new EventHandler<DataReceivedEventArgs>(server_DataReceived);
server.Start();
Console.WriteLine("Server Started");
Console.ReadKey();
}
static void server_DataReceived(object sender, DataReceivedEventArgs e)
{
Console.WriteLine("Receveived Data: " + Encoding.ASCII.GetString(e.Data));
}
}
using System;
using System.Collections.Generic;
using System.Net;
using System.Net.Sockets;
namespace TcpServerTest
{
public sealed class BeginEndTcpServer
{
private class Connection
{
public Guid id;
public byte[] buffer;
public Socket socket;
}
private readonly Dictionary<Guid, Connection> _sockets;
private Socket _serverSocket;
private readonly int _bufferSize;
private readonly int _backlog;
private readonly IPEndPoint serverEndPoint;
public BeginEndTcpServer(int bufferSize, int backlog, IPEndPoint endpoint)
{
_sockets = new Dictionary<Guid, Connection>();
serverEndPoint = endpoint;
_bufferSize = bufferSize;
_backlog = backlog;
}
public bool Start()
{
//System.Net.IPHostEntry localhost = System.Net.Dns.GetHostEntry(System.Net.Dns.GetHostName());
try
{
_serverSocket = new Socket(serverEndPoint.Address.AddressFamily, SocketType.Stream, ProtocolType.Tcp);
}
catch (System.Net.Sockets.SocketException e)
{
throw new ApplicationException("Could not create socket, check to make sure not duplicating port", e);
}
try
{
_serverSocket.Bind(serverEndPoint);
_serverSocket.Listen(_backlog);
}
catch (Exception e)
{
throw new ApplicationException("Error occured while binding socket, check inner exception", e);
}
try
{
//warning, only call this once, this is a bug in .net 2.0 that breaks if
// you're running multiple asynch accepts, this bug may be fixed, but
// it was a major pain in the ass previously, so make sure there is only one
//BeginAccept running
_serverSocket.BeginAccept(new AsyncCallback(AcceptCallback), _serverSocket);
}
catch (Exception e)
{
throw new ApplicationException("Error occured starting listeners, check inner exception", e);
}
return true;
}
public void Stop()
{
_serverSocket.Close();
lock (_sockets)
foreach (var s in _sockets)
s.Value.socket.Close();
}
private void AcceptCallback(IAsyncResult result)
{
Connection conn = new Connection();
try
{
//Finish accepting the connection
System.Net.Sockets.Socket s = (System.Net.Sockets.Socket)result.AsyncState;
conn = new Connection();
conn.id = Guid.NewGuid();
conn.socket = s.EndAccept(result);
conn.buffer = new byte[_bufferSize];
lock (_sockets)
_sockets.Add(conn.id, conn);
OnClientConnected(conn.id);
//Queue recieving of data from the connection
conn.socket.BeginReceive(conn.buffer, 0, conn.buffer.Length, SocketFlags.None, new AsyncCallback(ReceiveCallback), conn);
//Queue the accept of the next incomming connection
_serverSocket.BeginAccept(new AsyncCallback(AcceptCallback), _serverSocket);
}
catch (SocketException)
{
if (conn.socket != null)
{
conn.socket.Close();
lock (_sockets)
_sockets.Remove(conn.id);
}
//Queue the next accept, think this should be here, stop attacks based on killing the waiting listeners
_serverSocket.BeginAccept(new AsyncCallback(AcceptCallback), _serverSocket);
}
catch (Exception)
{
if (conn.socket != null)
{
conn.socket.Close();
lock (_sockets)
_sockets.Remove(conn.id);
}
//Queue the next accept, think this should be here, stop attacks based on killing the waiting listeners
_serverSocket.BeginAccept(new AsyncCallback(AcceptCallback), _serverSocket);
}
}
private void ReceiveCallback(IAsyncResult result)
{
//get our connection from the callback
Connection conn = (Connection)result.AsyncState;
//catch any errors, we'd better not have any
try
{
//Grab our buffer and count the number of bytes receives
int bytesRead = conn.socket.EndReceive(result);
//make sure we've read something, if we haven't it supposadly means that the client disconnected
if (bytesRead > 0)
{
//put whatever you want to do when you receive data here
conn.socket.Receive(conn.buffer);
OnDataReceived(conn.id, (byte[])conn.buffer.Clone());
//Queue the next receive
conn.socket.BeginReceive(conn.buffer, 0, conn.buffer.Length, SocketFlags.None, new AsyncCallback(ReceiveCallback), conn);
}
else
{
//Callback run but no data, close the connection
//supposadly means a disconnect
//and we still have to close the socket, even though we throw the event later
conn.socket.Close();
lock (_sockets)
_sockets.Remove(conn.id);
}
}
catch (SocketException)
{
//Something went terribly wrong
//which shouldn't have happened
if (conn.socket != null)
{
conn.socket.Close();
lock (_sockets)
_sockets.Remove(conn.id);
}
}
}
public bool Send(byte[] message, Guid connectionId)
{
Connection conn = null;
lock (_sockets)
if (_sockets.ContainsKey(connectionId))
conn = _sockets[connectionId];
if (conn != null && conn.socket.Connected)
{
lock (conn.socket)
{
//we use a blocking mode send, no async on the outgoing
//since this is primarily a multithreaded application, shouldn't cause problems to send in blocking mode
conn.socket.Send(message, message.Length, SocketFlags.None);
}
}
else
return false;
return true;
}
public event EventHandler<ClientConnectedEventArgs> ClientConnected;
private void OnClientConnected(Guid id)
{
if (ClientConnected != null)
ClientConnected(this, new ClientConnectedEventArgs(id));
}
public event EventHandler<DataReceivedEventArgs> DataReceived;
private void OnDataReceived(Guid id, byte[] data)
{
if (DataReceived != null)
DataReceived(this, new DataReceivedEventArgs(id, data));
}
public event EventHandler<ConnectionErrorEventArgs> ConnectionError;
}
public class ClientConnectedEventArgs : EventArgs
{
private readonly Guid _ConnectionId;
public Guid ConnectionId { get { return _ConnectionId; } }
public ClientConnectedEventArgs(Guid id)
{
_ConnectionId = id;
}
}
public class DataReceivedEventArgs : EventArgs
{
private readonly Guid _ConnectionId;
public Guid ConnectionId { get { return _ConnectionId; } }
private readonly byte[] _Data;
public byte[] Data { get { return _Data; } }
public DataReceivedEventArgs(Guid id, byte[] data)
{
_ConnectionId = id;
_Data = data;
}
}
public class ConnectionErrorEventArgs : EventArgs
{
private readonly Guid _ConnectionId;
public Guid ConnectionId { get { return _ConnectionId; } }
private readonly Exception _Error;
public Exception Error { get { return _Error; } }
public ConnectionErrorEventArgs(Guid id, Exception ex)
{
_ConnectionId = id;
_Error = ex;
}
}
我的问题是:服务器只收到一部分数据(在示例中它只收到“EFGHA1B2”)。另外,如果我只发送 4 字节的数据,服务器在连接关闭之前不会收到它。 我错过了什么或做错了什么?
另一件事是,目前我真的对不同的可能性感到困惑,我这样做是不是一个好的解决方案?或者我应该尝试其他方法吗?
如有任何帮助,我们将不胜感激!
最佳答案
我怀疑套接字仅在收到的字节数等于您在调用 BeginReceive 时指定的长度或套接字关闭时才调用您的回调方法。
我认为您需要问自己的问题是您将通过此连接发送的数据的性质是什么。数据是否真的是不间断的字节流,例如文件的内容?如果是这样,那么也许您可以合理地期望客户端发送所有字节,然后立即关闭连接。如您所说,如果客户端关闭连接,则将调用您的回调方法以获取剩余字节。
如果连接将保持打开状态并用于发送单独的消息,那么您可能需要为该通信设计一个简单的协议(protocol)。客户端是否会发送多个任意长的字符串,服务器是否需要分别处理每个字符串?如果是这样,那么一种方法可能是为每个字符串添加一个整数值(假设为 4 个字节)作为前缀,该整数值指示您将发送的字符串的长度。然后您的服务器可以首先调用 BeginReceive 指定 4 个字节的长度,使用这 4 个字节来确定传入字符串的长度,然后调用 Receive 指定传入字符串的长度。如果传入字符串的长度超过缓冲区的大小,那么您也需要处理这种情况。
我已经创建了一个实现这种方法的小型示例服务器和客户端应用程序。我将缓冲区硬编码为 2048 字节,但如果您指定一个小至 4 字节的缓冲区,它仍然有效。
在我的方法中,如果传入数据超过我现有缓冲区的大小,那么我会创建一个单独的字节数组来存储传入数据。这可能不是处理这种情况的最佳方式,但我认为您如何处理这种情况取决于您实际对数据执行的操作。
using System;
using System.Collections.Generic;
using System.Linq;
using System.Net;
using System.Net.Sockets;
using System.Text;
namespace SocketServer
{
class Connection
{
public Socket Socket { get; private set; }
public byte[] Buffer { get; private set; }
public Encoding Encoding { get; private set; }
public Connection(Socket socket)
{
this.Socket = socket;
this.Buffer = new byte[2048];
this.Encoding = Encoding.UTF8;
}
public void WaitForNextString(AsyncCallback callback)
{
this.Socket.BeginReceive(this.Buffer, 0, 4, SocketFlags.None, callback, this);
}
}
class Program
{
static void Main(string[] args)
{
Connection connection;
using (Socket listener = new Socket(AddressFamily.InterNetwork, SocketType.Stream, ProtocolType.Tcp))
{
listener.Bind(new IPEndPoint(IPAddress.Loopback, 6767));
listener.Listen(1);
Console.WriteLine("Listening for a connection. Press any key to end the session.");
connection = new Connection(listener.Accept());
Console.WriteLine("Connection established.");
}
connection.WaitForNextString(ReceivedString);
Console.ReadKey();
}
static void ReceivedString(IAsyncResult asyncResult)
{
Connection connection = (Connection)asyncResult.AsyncState;
int bytesReceived = connection.Socket.EndReceive(asyncResult);
if (bytesReceived > 0)
{
int length = BitConverter.ToInt32(connection.Buffer, 0);
byte[] buffer;
if (length > connection.Buffer.Length)
buffer = new byte[length];
else
buffer = connection.Buffer;
int index = 0;
int remainingLength = length;
do
{
bytesReceived = connection.Socket.Receive(buffer, index, remainingLength, SocketFlags.None);
index += bytesReceived;
remainingLength -= bytesReceived;
}
while (bytesReceived > 0 && remainingLength > 0);
if (remainingLength > 0)
{
Console.WriteLine("Connection was closed before entire string could be received");
}
else
{
Console.WriteLine(connection.Encoding.GetString(buffer, 0, length));
}
connection.WaitForNextString(ReceivedString);
}
}
}
}
using System;
using System.Collections.Generic;
using System.Linq;
using System.Net;
using System.Net.Sockets;
using System.Text;
namespace SocketClient
{
class Program
{
static void Main(string[] args)
{
var encoding = Encoding.UTF8;
using (var connector = new Socket(AddressFamily.InterNetwork, SocketType.Stream, ProtocolType.Tcp))
{
connector.Connect(new IPEndPoint(IPAddress.Loopback, 6767));
string value;
value = "1234";
Console.WriteLine("Press any key to send \"" + value + "\".");
Console.ReadKey();
SendString(connector, encoding, value);
value = "ABCDEFGH";
Console.WriteLine("Press any key to send \"" + value + "\".");
Console.ReadKey();
SendString(connector, encoding, value);
value = "A1B2C3D4E5F6";
Console.WriteLine("Press any key to send \"" + value + "\".");
Console.ReadKey();
SendString(connector, encoding, value);
Console.WriteLine("Press any key to exit.");
Console.ReadKey();
connector.Close();
}
}
static void SendString(Socket socket, Encoding encoding, string value)
{
socket.Send(BitConverter.GetBytes(encoding.GetByteCount(value)));
socket.Send(encoding.GetBytes(value));
}
}
}
关于c# - 在 C# 中做正确和快速的 TCP 网络,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/8082788/
我正在查看instance_variable_set的文档并看到给出的示例代码是这样做的:obj.instance_variable_set(:@instnc_var,"valuefortheinstancevariable")然后允许您在类的任何实例方法中以@instnc_var的形式访问该变量。我想知道为什么在@instnc_var之前需要一个冒号:。冒号有什么作用? 最佳答案 我的第一直觉是告诉你不要使用instance_variable_set除非你真的知道你用它做什么。它本质上是一种元编程工具或绕过实例变量可见性的黑客攻击
question的一些答案关于redirect_to让我想到了其他一些问题。基本上,我正在使用Rails2.1编写博客应用程序。我一直在尝试自己完成大部分工作(因为我对Rails有所了解),但在需要时会引用Internet上的教程和引用资料。我设法让一个简单的博客正常运行,然后我尝试添加评论。靠我自己,我设法让它进入了可以从script/console添加评论的阶段,但我无法让表单正常工作。我遵循的其中一个教程建议在帖子Controller中创建一个“评论”操作,以添加评论。我的问题是:这是“标准”方式吗?我的另一个问题的答案之一似乎暗示应该有一个CommentsController参
如何在ruby中调用C#dll? 最佳答案 我能想到几种可能性:为您的DLL编写(或找人编写)一个COM包装器,如果它还没有,则使用Ruby的WIN32OLE库来调用它;看看RubyCLR,其中一位作者是JohnLam,他继续在Microsoft从事IronRuby方面的工作。(估计不会再维护了,可能不支持.Net2.0以上的版本);正如其他地方已经提到的,看看使用IronRuby,如果这是您的技术选择。有一个主题是here.请注意,最后一篇文章实际上来自JohnLam(看起来像是2009年3月),他似乎很自在地断言RubyCL
我喜欢使用Textile或Markdown为我的项目编写自述文件,但是当我生成RDoc时,自述文件被解释为RDoc并且看起来非常糟糕。有没有办法让RDoc通过RedCloth或BlueCloth而不是它自己的格式化程序运行文件?它可以配置为自动检测文件后缀的格式吗?(例如README.textile通过RedCloth运行,但README.mdown通过BlueCloth运行) 最佳答案 使用YARD直接代替RDoc将允许您包含Textile或Markdown文件,只要它们的文件后缀是合理的。我经常使用类似于以下Rake任务的东西:
我想在Ruby中创建一个用于开发目的的极其简单的Web服务器(不,不想使用现成的解决方案)。代码如下:#!/usr/bin/rubyrequire'socket'server=TCPServer.new('127.0.0.1',8080)whileconnection=server.acceptheaders=[]length=0whileline=connection.getsheaders想法是从命令行运行这个脚本,提供另一个脚本,它将在其标准输入上获取请求,并在其标准输出上返回完整的响应。到目前为止一切顺利,但事实证明这真的很脆弱,因为它在第二个请求上中断并出现错误:/usr/b
我一直致力于让我们的Rails2.3.8应用程序在JRuby下正确运行。一切正常,直到我启用config.threadsafe!以实现JRuby提供的并发性。这导致lib/中的模块和类不再自动加载。使用config.threadsafe!启用:$rubyscript/runner-eproduction'pSim::Sim200Provisioner'/Users/amchale/.rvm/gems/jruby-1.5.1@web-services/gems/activesupport-2.3.8/lib/active_support/dependencies.rb:105:in`co
我正在尝试在Ruby中复制Convert.ToBase64String()行为。这是我的C#代码:varsha1=newSHA1CryptoServiceProvider();varpasswordBytes=Encoding.UTF8.GetBytes("password");varpasswordHash=sha1.ComputeHash(passwordBytes);returnConvert.ToBase64String(passwordHash);//returns"W6ph5Mm5Pz8GgiULbPgzG37mj9g="当我在Ruby中尝试同样的事情时,我得到了相同sha
我需要一些关于TDD概念的帮助。假设我有以下代码defexecute(command)casecommandwhen"c"create_new_characterwhen"i"display_inventoryendenddefcreate_new_character#dostufftocreatenewcharacterenddefdisplay_inventory#dostufftodisplayinventoryend现在我不确定要为什么编写单元测试。如果我为execute方法编写单元测试,那不是几乎涵盖了我对create_new_character和display_invent
C#实现简易绘图工具一.引言实验目的:通过制作窗体应用程序(C#画图软件),熟悉基本的窗体设计过程以及控件设计,事件处理等,熟悉使用C#的winform窗体进行绘图的基本步骤,对于面向对象编程有更加深刻的体会.Tutorial任务设计一个具有基本功能的画图软件**·包括简单的新建文件,保存,重新绘图等功能**·实现一些基本图形的绘制,包括铅笔和基本形状等,学习橡皮工具的创建**·设计一个合理舒适的UI界面**注明:你可能需要先了解一些关于winform窗体应用程序绘图的基本知识,以及关于GDI+类和结构的知识二.实验环境Windows系统下的visualstudio2017C#窗体应用程序三.
网络编程套接字网络编程基础知识理解源`IP`地址和目的`IP`地址理解源MAC地址和目的MAC地址认识端口号理解端口号和进程ID理解源端口号和目的端口号认识`TCP`协议认识`UDP`协议网络字节序socket编程接口`sockaddr``UDP`网络程序服务器端代码逻辑:需要用到的接口服务器端代码`udp`客户端代码逻辑`udp`客户端代码`TCP`网络程序服务器代码逻辑多个版本服务器单进程版本多进程版本多线程版本线程池版本服务器端代码客户端代码逻辑客户端代码TCP协议通讯流程TCP协议的客户端/服务器程序流程三次握手(建立连接)数据传输四次挥手(断开连接)TCP和UDP对比网络编程基础知识