client-socket | A pure-Typescript library to interact with Discord 's Gateway | Chat library

I have a requirement to send data asynchronously via TCP. It is a collection of strings ICollection.

I searched and found a good starting example from Microsoft (see below). The sample seems to be under .NET Framework, but I assume it applies to .NET Core as well.

What I am doing:

1. I am re-purposing the code as a non-static class

2. I would like to send a collection of strings ICollection. I know I can rewrite it to send the collection of strings in the main method. Not a problem.

3. I would like to receive a response for each message sent and do something with it. The current response is stored statically in private static String response = String.Empty;. I don't want it to be static. I want a local method variable.

4. My challenge begins from item 3.. How do I return back that response message that seems only accessible from within private static void ReceiveCallback( IAsyncResult ar )

   I do not think changing it to private static string ReceiveCallback( IAsyncResult ar ) would work. If so, how do I read it from client.BeginReceive( state.buffer, 0, StateObject.BufferSize, 0, new AsyncCallback(ReceiveCallback), state);?

I put out a 300point bounty on a very old post for a similar question I found: C# Asyn. Socket Programming. Happy to award anyone who answers here, then there.

An additional question is: Is it recommended practice to open a TCP connection, send the multiple messages, then close it? Or to open a TCP connection for each message being sent?

Microsoft Example

i use this code for working with Port

https://docs.microsoft.com/en-us/dotnet/framework/network-programming/asynchronous-client-socket-example

but I get the following error. No connection could be made because the target machine actively refused it.

Should I not connect(bind) the socket to the port?

When I start Express, it crashes in about 5 minutes.

Use this dependencies.

• express 4.17.1
• mongoose 5.9.7
• tunnel-ssh 4.1.4

wait about 5 min after, got an error like this.

I am trying to recreate Microsoft's .net examples for simple client/server communication in an c# uwp app. Later on I would like to send simple data from one app to another.

Asynchronous Client Socket Example https://docs.microsoft.com/en-us/dotnet/framework/network-programming/asynchronous-client-socket-example

Asynchronous Server Socket Example https://docs.microsoft.com/en-us/dotnet/framework/network-programming/asynchronous-server-socket-example

I haven't made any crucial changes but modified the ipHostInfo like this:

I've successfully created a simple server and client application in C# that communicate asynchronously between the server and multiple clients, i used the following Microsoft Docs to create it:

https://docs.microsoft.com/en-us/dotnet/framework/network-programming/asynchronous-server-socket-example

https://docs.microsoft.com/en-us/dotnet/framework/network-programming/asynchronous-client-socket-example

They are both working fine, but my question is, i want to execute an action every second on the server and i don't know the best way to go about it. Should i use something like the Timer class to do it? Is using a Timer interfere in any way with the calls that the server is receiving from the clients?

I'm sending UDP packets (statsd) from pods on a host to :8125. On the other end, a collector (datadog-agent using hostPort; one per host via DaemonSet) picks up the packets and does it's thing.

Generally this works fine, but if I ever delete + re-create the collector (kubectl delete pod datadog-agent-xxxx; new pod is started on same IP/port a few seconds later), traffic from existing client-sockets stop arriving at the collector (UDP sockets created after the pod-rescheduling works fine).

Re-starting just the agent inside the collector pod (kubectl exec -it datadog-agent-xxxxx agent stop; auto-restarts after ~30s) the same old traffic does show up. So containers somehow must have an impact.

While UDP are (supposedly) stateless, something, somewhere is obviously keeping state around!? Any ideas/pointers?

Each "client" pod has something like this in the deployment/pod:

I'm calling another python file from the current file, and using a function that calls all functions in the other file.

I'm using this example from Asynchronous Client Socket Example

I am trying to learn socket programming in C# By using google I found a lot of good tutorials and examples. But here is my own code :

Sender application :