The thinking at the time that a queue for incoming requests and a pool of threads, one thread per request was best.ĭata would suggest that Java NIO scales better, JBOSS maintains and uses it now. I think history sheds some light on the answer. I'm looking for comments on performance, ease of use, scalability (both in how well it scales development wise and usage wise), security, and any other base you think you may put information on.Īnyways, any input would be greatly appreciated. Though I'm asking about Java (because it's what I'm most comfortable with) specifically, you are more than welcome to expand this to any other languages. using Java's NIO or a networking framework like Mina (which I'm using) or Netty (which I want to play around with at some point). Though for the class, this is how the project needs to be done, I was wondering about the advantages/disadvantages of using something like Tomcat or a similar web server to receive all incoming communication, vs.
Currently for a class, I'm implementing a server which receives two types of connections, using TCP, and a custom application layer protocol.
0 kommentar(er)
