Home/ Questions/Q 9217791
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-18T02:42:44+00:00

I have a multi-threaded application, where different components (running in different threads) needs to

  • 0

I have a multi-threaded application, where different components (running in different threads) needs to send out UDP messages. For now they all share the same Socket instance.

The socket is created as Socket socket = new Socket(AddressFamily.InterNetwork, SocketType.Dgram, ProtocolType.Udp) and socket.Send(byte[] message) is called from the threads. Socket.Send is the only method that is called.

Is this a bad approach? I haven’t seen any problems yet, but I fear that this is not the way sockets were intended to be used.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    the most “correct” solution is to create a method that calls the socket.send method and protect this call by using a lock or mutex. This way wikl garantee that socket object is used for once thread at a given time. You can also archieve this by using a queue.

    • 0