jgauffin
commented
9 years ago You have to choose strategy if you want robustness. In your case I would probably code a client by using TcpChannel directly.
Something like this:
public class ClientExample
{
private readonly TcpChannel _channel;
public ClientExample()
{
MessageEncoding = Encoding.UTF8;
_channel = new TcpChannel(
new BufferSlice(new byte[65535], 0, 65535),
new YourEncoder(),
new YourDecoder())
{MessageReceived = OnMessage};
_channel.Disconnected += OnDisconnect;
}
private void OnDisconnect(ITcpChannel channel, Exception exception)
{
if (Disconnected != null)
Disconnected(this, EventArgs.Empty);
}
public void Connect(string remoteHost, int port)
{
//this client do not reconnect or try to connect again if the first attempt fails.
//you need to code that by yourself.
var socket = new Socket(AddressFamily.InterNetwork, SocketType.Stream, ProtocolType.Tcp);
socket.Connect(remoteHost, port);
_channel.Assign(socket);
}
private void OnMessage(ITcpChannel channel, object message)
{
//Will be invoked once a message arrives,
//i.e. no need for polling
}
public void Send(string message)
{
_channel.Send(message);
}
public event EventHandler Disconnected;
}
Tochemey
I have implemented the client using the ChannelTcpClient. I can send data to the upstream socket server and receive response. However I want to be reading some data via a different thread and at the same time sending data and reading response as usual. What I observe is that the polling thread has already remove my response data. So I went to the ChannelTcpClient ReceiveAync and I discovered that it uses a concurrent queue which means FIFO. I would like to know whether I am doing the right thing or there is a way to do polling as well as send request and receive response using ReceiveAsync.