I implemented a middleware in Netty based on the HexDumpProxy example:
BROWSER ------> WEBAPP ------> MW-NETTY ------> SERVER
[http] [http] [tcp]
The MW-NETTY (see above) needs to connect to the SERVER using a port number
different for each customer (the WEBAPP is dedicated by customer).
So, as a last resort, the TCP port could be disabled to preserve the
SERVER...
The client id is transported in an HTTP header from WEBAPP to MW-NETTY.
As the channels are created before messages arrive, what would be the best
strategy?
Thanks,
--nick
--
You received this message because you are subscribed to the Google Groups
"Netty discussions" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/netty/fc006c41-2310-4d8d-aa77-120ee5c134ba%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
