Hi, Filip Defoort wrote:
> So, a couple of questions and suggestions: > 1/ Q: exactly why are proxy objects used ? I can see one use, and that > is preventing people from > accidentally calling lifecycle methods.. [which is by the way a really > nifty feature, but see 3/]. AFAIK, this is the main if not only purpose of using component proxys in Fortress. Using proxys could also provide the groundwork for an interceptor framework, allowing the container to dynamically add functionality to components, but that's speculative. > 3/ S: if 1/ is correct, why don't we have a debug and a release mode of > a container... Running > a container in debug mode would enable the container to use proxies and > allow the developer > to test his code properly -- running in release mode would use the > regular componentfactory > and have no penalty.. There's really no need for checking the lifecycle > methods usage at > runtime in a release system..(afaik.. ;-) ). To me, it sounds like a good idea. I could imagine that this approach might be insufficient for very complex applications where code coverage could become an issue. Just my 2ct, Olaf --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
