You'd want a "synchronized" clause around any reads or writes to make sure you send a complete message or receive a complete message with no interferance from other threads. You're kinda doing your own multiplexing. It will be an interesting server on the other end that can figure out the inbound messages!
A good question is never answered. It is not a bolt to be tightened into place but a seed to be planted and to bear more seed toward the hope of greening the landscape of the idea. John Ciardi
You can try to create a queue and queue reader that sends data over the sockets. The other threads will put messages on that queue.
posted 16 years ago
Originally posted by Yaroslav Chinskiy: You can try to create a queue and queue reader that sends data over the sockets. The other threads will put messages on that queue.
Multiple threads on the client side need to establish connection to different servers.If thread T1 needs to send data to IP1 and thread T2 also needs to send data to IP1, T2 needs to wait for the socket descriptor to get free. Would it improve performance by opening multiple socket descriptors for each Thread,on the client end, so that simultaneously messages can be sent??
I do some of my very best work in water. Like this tiny ad: