Hi,
As Grizzly offers various way of creating/handling connections, do you have
a recommended way of doing so?
In my case, I would like to play around with Grizzly by creating something
like a TCP proxy where it routes connection from one host/port to another
host/port. On the server side, I create a filter to listen "READ" event and
write into another NIO transport to the target server. The problem I have is
that now I need to listen to "READ" event from both sides to write the
output to the other side. Having two filters to two transports seem to make
the code very messy. Is there any suggestion to make it simpler?
--
View this message in context: http://www.nabble.com/Grizzly-2.0M1-Best-Practice-tp23398139p23398139.html
Sent from the Grizzly - Users mailing list archive at Nabble.com.