I'm new to both NIO and Grizzly and would like to know if they are
appropriate for the application that I'm writing. Essentially I am writing a
game server that needs to host many games. Each game has two associated
players. I want the players to be able to submit requests and receive
responses, but I also want the server to be able to push messages back to
the players. A common scenario would be that player 1 makes a move by
issuing a request, the server responds to player 1 but also sends
information to player 2 (without player 2 making a request).
In the pre-NIO world, I would associate a thread per user and keep the
socket connection open... This doesn't scale particularly well and I know
NIO was designed to improve on this paradigm with non-blocking IO. How
would I do something like this using NIO and (better yet) Grizzly?
Thanks in advance,
Bill
--
View this message in context: http://www.nabble.com/Grizzly-and-NIO-neo-needs-advice-tp19629288p19629288.html
Sent from the Grizzly - Users mailing list archive at Nabble.com.