Lazy initialization is not a good use for that. 100% agreement there. Do
you find yourself doing that a lot? I've never gone that route, prefering
monolithic initialization blocks. I can see some benefits, but they seem
small for the headaches (you mentioned the big one). Just curious.
I mostly go for lazy initialization using a getXxxx() method in the fa�ade to initialize the shared scope entity on demand.
macromedia.com's applications use a mixture of initialization block (our application 'bootstrap' which uses a semaphore variable to indicate the entire bootstrap is complete) and lazy initialization.
Regards, Sean
---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev' in the message of the email.
CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com).
An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED]
