bootstrap.setOption("child.<parameter>", value) vs. bootstrap.setOption("<parameter>", value)

[Squigly]

I'm sorry, let me rephrase:
The "father" in itself has no meaning for tcpnodelay or recieveBuffer or
anything else, as it's not actually representing an active connection, It's
the child connection that actually uses those parameters, so,
what exactly would be the diff if I'll set tcpnodelay on the child, and not
on the father?
what effect would I have to put X receiveBuffer on the father, and Y on the
child?
-- 
View this message in context: http://n2.nabble.com/bootstrap-setOption-child-parameter-value-vs-bootstrap-setOption-parameter-value-tp4772200p4773294.html
Sent from the Netty User Group mailing list archive at Nabble.com.