Hi Peter!
On Tue, Jul 16, 2002 at 10:04:43AM -0400, Peter Royal wrote:
> On Tuesday 16 July 2002 10:07 am, Marcus Crafter wrote:
> > 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 ?
>
> I'm +1 on #3, as I do believe that was the intended deafault.
I think so too.
> setCommandQueue( null ) won't work to disable async though, we would need
> something like setSynchronousInitialization( true ).
Why wouldn't it work ? It seems like AbstractContainer was built
to handle if the command queue was null (it checks for null before
queueing operations).
Was there a technical reason why it wouldn't work, or did you mean
that the actual operation of passing null to the setCommandQueue()
method wasn't obvious enough ?
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]>
