On Nov 5, 2009, at 4:17 AM, Mike Schrag wrote:
You mean you would have thought didFinishLaunching() was better?
Yes.
So the other one actually is the right place, as it turns out ...
The startup process is:
willFinishLanching (which calls wonder's finishInitialization)
finishInitialization
migrationsWillRun
...migrate...
migationsDidRun
create worker threads
didFinishLaunching
So this actually makes sense now why it would be safer to go in
willFinishLaunching. If you use migrations, you should probably put
this code in migrationsDidRun instead, though. I still don't get
why it's a problem now that we have the lock in around the loading
process, but ... whatever. I think this is the right place for his
initialization.
Curses, your right! I'd forgotten that didFinishLaunching is sent
after request processing starts. That has never made sense to me.
And that totally explains the "seems like concurrent threads are
running" - they are!
Chuck
--
Chuck Hill Senior Consultant / VP Development
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
