On Mar 4, 2006, at 12:38 AM, Trustin Lee wrote:
what i'd like to see, is a ThreadPoolFilter that just manages withreading in events and putting them into per-session queues, and then we can plug in threading strategies.. I may plug in a ThreadPoolExecutor strategy, others could use the existing leader/ follower strategy.It will be very great if we can, but we also should design the thread pool interface so it can cover both normal and L-F thread pools. I think we cando this. You interested? :)
I'll see what I can do :)
Actually, we can just remove init()and destroy() and let IoFilter imeplementations choose when to init and destroy itself (e.g. a filter could destroy itself when it is removed from all session filter chains. Without init() and destroy() everything becomes very simple and we don't need to do lifecycle management globally at all.Does this make sense?
Makes sense, I like it! -pete -- [EMAIL PROTECTED] - http://fotap.org/~osi
smime.p7s
Description: S/MIME cryptographic signature
