Java in 2011: threaded sockets VS NIO: what to choose on 64bit OS and latest Java version?

And Can't get past 2542 Threads in Java on 4GB iMac OSX 10.6.3 Snow Leopard (32bit) ).

And Can't get past 2542 Threads in Java on 4GB iMac OSX 10.6.3 Snow Leopard (32bit)). To reach that many threads you'll probably need to adjust the stack size of the JVM.

Another thing to note is if you're using all those connections to talk to a server (i.e. You're the client side of the connection), you're limited to about 65,000 connections due to the number of local ports available. – Adam Bryzak Mar 25 at 20:31 No, you are not.

Each client connects to the same port. BTW, I take those threads as there is no hard limit? What Paul Tuma says here then: paultyma.blogspot.Com/2008/03/… – FractalizeR Mar 25 at 20:38 They connect to the same port on the server side, but client connections still need to allocate a port locally to receive a response from the server.

– Adam Bryzak Mar 25 at 20:42 This cannot be true because in this case these will be the lies: groovy.dzone. Com/articles/512000-concurrent-websockets | coversant.Net/product/soapboxserver. Aspx : they both tell about concurrent connections on a single machine.

– FractalizeR Mar 25 at 20:46 2 @FractalizeR: It is correct. Each outgoing connection needs a unique port number in current TCP implementations. In theory it is possible for a TCP/IP stack to take notice of the tuple when allocating the outgoing port; in practice it is impossible due to the API: specifically the fact that bind() happens before connect(), whether explicitly or implictly.

– EJP Mar 257 at 10:02.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.