Hi All,
Hope all is well.
Last week I brought up a couple of questions about Fortress, one
of them was the issue we currently have with it's async initialization.
Essentially it doesn't work unless you provide a CommandQueue to
AbstractContainer manually that is registered with a
ThreadManager. The default one created by the ContextManager isn't
registered with any ThreadManager, and hence remains inactive.
The proposed solutions so far include:
1. Create two abstract containers, one that does lazy
initialization and one that does async initialization (ie. one
base class with a ThreadManager registered CommandManager, and one
without).
2. Change ContextManager so that it doesn't create a CommandManager
by default if none is supplied to it (ie. have sync init as the
default).
3. Change ContextManager so that it creates a ThreadManager registered
CommandManager by default if none is supplied to it (ie. have async
init by default).
4. Any others ?
I'd like to do the 3rd, ie. have async init by default with a
ThreadManager registered CommandManager, if the user doesn't
provide one via setCommandQueue().
I also think it would be a good idea if we had an explicit way to
disable async init as Peter proposed, either via
setCommandQueue(null), or some config option or some other way ?
What do you think ?
Cheers,
Marcus
--
.....
,,$$$$$$$$$, Marcus Crafter
;$' '$$$$: Computer Systems Engineer
$: $$$$: ManageSoft GmbH
$ o_)$$$: 82-84 Mainzer Landstrasse
;$, _/\ &&:' 60327 Frankfurt Germany
' /( &&&
\_&&&&'
&&&&.
&&&&&&&:
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
