On Apr 30, 2007, at 3:40 PM, Trustin Lee wrote:
Since a class instance will only be in a single filter chain once (even if its used for multiple sessions), if the filter appended a number to its attributes, such as its hashcode, that'd provide uniqueness?We might need to allow the same instance of IoFilter to be inserted more than once to one filter chain, which makes hashcode useless. Logging filter is a good example. A user can insert the same logging filter instance before and after the codec filter for debugging purpose. Hmmm... but just adding small restriction (i.e. no same filter instances in a chain) might make things much easier. :D WDYT?
I think its fair to say that for our filters, if you want to use them in a chain multiple times, you need unique instances.
I don't think it needs to be a general restriction for all filters.. -pete -- [EMAIL PROTECTED] - http://fotap.org/~osi
smime.p7s
Description: S/MIME cryptographic signature
