I would let all the parts in a chain implement the same WebRequest interface for example, and than walk through this chain to let all parts do their work. I agree that there may be some combinations that migth break the chain, for example a security interceptor that will block further handling.
2008/4/11, Maurice Marrink <[EMAIL PROTECTED]>: > > On Fri, Apr 11, 2008 at 9:46 AM, Martijn Lindhout > <[EMAIL PROTECTED]> wrote: > > Can't we implement 'something' using an interceptor chain? Extensions > can > > register themselves in the Application#init() method. There might be a > chain > > for the webrequest cycle, for example. Each part in the chain may add > some > > behavior to the cycle then. > > And how would conflicts be resolved then? for instance 2 extensions > that both require a custom websession? > Even when using proxies this could get tricky if both try to implement > the same method. whichever implementation wins your app will not work > properly. > I am afraid in those kinds of situations you still end up manually > merging the 2 implementations (if possible). > > > Maurice > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Martijn Lindhout JointEffort IT Services http://www.jointeffort.nl [EMAIL PROTECTED] +31 (0)6 18 47 25 29
