>> And if the NextFilters per chain ** are ** different per session, can
>> we live with that? (I.e, it means that if a filter wants to fire an >> event, it must map sessions to NextFilters - or must look it up). > I think this is perfectly fine. But that's just me. :) As I see it, this is the only difference between the "smart-NextFilter" approach, and the simple chain approach. So, if everyone agrees that multiple inits / multiple NextFilters isn't a problem, then I vote for ditching the "smart-NextFilter" approach - as it doesn't add any value. Im so glad this is starting to sound very simple :o) > /Niklas 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.
