>> What about per filter
initialisation?
>> I was
thinking that a filter would be inited the first time it was employed (i.e,
first session for acceptor filters,
>> first
session on port for port filters, and per session for session
filters).
> It might, but it might not if it just initializes its per-session state in init(). So init() should
> be invoked every time it is added to a
per-session chain to support
>
both use case. Any better idea on this?
I
definately dont have any better ideas. I can definately call init / destroy on a
per filter per session basis if thats what is wanted.
I
originally thought it might be cleaner for users if the two use cases are
separated (filter initialisation - which may be used for many sessions, and
session initialisation which is per session) - but I've got no strong feelings
either way :o) (The "NextFilter" would be
the same object for all invocations in practice anyway)
Trustin
what we call human nature is actually human habit
--
http://gleamynode.net/
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.
