Hi, On Sat, 1 Feb 2003 08:42, David Worms wrote: > > 6. It appears to me that Fortress is creating proxy components that > > act as > > facades to the underlying component interfaces (am I right here?). > > This is > > exactly what I wanted to avoid. It simply becomes too heavy weighted > > (unless > > we use typical component patterns). Since we may well create 100,000 > > URLMessages per second, it would kill us to send every call to > > urlMessageFactory.createURLMessage through a proxy. I wonder if the > > other > > available containers work the same way? (I know Phoenix doesn't do > > this) > > I am not sure about this. Can someone help us? I think we should look > at the component handlers (the lifestyle) in Fortress: > org.apache.excalibur.fortress.handler package.
Actually all the modern containers proxy the services. This does come with some overhead because we use generic JDK1.3 proxy mechanism combined with reflection during invocation. This could be massively optimized by creating proxys using BCEL (and that is something in the works I believe). However the overhead should not be too much. If it does become an issue then give us a heads up and we will fix it. -- Cheers, Peter Donald ------------------------------------------------------------ militant agnostic: i don't know, and you don't know either. ------------------------------------------------------------ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
