Tim Lucas wrote:No. 2)
Now if you have a custom type with a displayMethod containing a rule then this won't get called either. This limiting only to dmHTML and dmInclude seems only an optimisation, because AFAIK oCon.delete() doesn't care whether there's any container instances for the object -- it will just delete any it finds.
Wouldn't it be best to eliminate this type check altogether and just call oCon.delete() regardless?
I think yes... though this might have changed slightly with the introduction of container reflection in 2.3. Any changes would need to take into consideration the impact of new form of shared containers.
Not too familiar with these new changes. Have they been finalised? I'd be interested on hearing more about them.
Also, I suspect that the method could cal the factory service for container.cfc rather than instantiating another copy of the CFC (though hardly an essential optimisation during a delete).
Yeah, though the tendency to move objects into app scope for efficiency means that everything tends towrds static factory services -- rarely does anything end up as an entity object.
-- tim lucas
http://www.toolmantim.com
--- You are currently subscribed to farcry-dev as: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
