> So, there is no way for me to impose a Blacklist filter specific to a handler before I do SSL > and all other stuff someone else has configured already at port level?
Every filter has the ability to know what handler a filter invocation applies to if it really needs to (Each filter method is given a IoSession. Then there is IoSession#getHandler). > Session level filters should only be used in very specific cases related to the actual session you are working with. > Hence, lazy copying will be reduced to a minimum. So presumably your blacklist filter would be at the port (or even session manager) level - in which case you would configure it to come before SSL. Could you explain the problem further as Im not understanding how the proposed chains wouldn't work for your example. Dave This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.
