marc fleury wrote: > |Well, the only thing the incoming gates would have to know is to > |immediately delegate to the stack configuration MBean. After that it can > |take care of the stack config. > | > |*But this will only work if the interceptor/config interleaving is done > |as outlined in previous post*. Otherwise it will be an MBean explosion... > > 4 hours of sleep and I need coffee but no I think that you don't have > explosion as we now know that you can use stateless interceptor which > enables you to have ONE instance per node as well as "at the beginning" > mapping that the MI sees coming in, no need to go through the config > interceptor every call. > > Do you agree?
Let's see if I understand this right. Do you send the list of interceptors as part of the MI? I.e. the list contains the MI and an index, and each interceptor just increases the index and delegates to the next? Or how is the stack controlled? What is the driver of the interceptor delegation? /Rickard -- Rickard �berg Software Development Specialist xlurc - Xpedio Link�ping Ubiquitous Research Center Author of "Mastering RMI" Email: [EMAIL PROTECTED] _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
