On Monday 08 July 2002 01:04 pm, Berin Loritsch wrote: > > In the ContextManager a default CommandQueue object is > > created if one > > is not specified (and also if setCommandQueue(null) is > > given to the > > ContextBuilder (which seems suspicious)) and there > > seems to be no > > ThreadManager associated with the CommandQueue, so > > initialize()'s are > > only done inside FortressComponent/ServiceManager.lookup(). > > We need to make the CommandManager initialize a default ThreadManager > if one isn't provided.
Is that really what we want? Currently there is no way to *not* use the async init (other than exploiting the above bug). It'd be nice to keep that option. -pete -- peter royal -> [EMAIL PROTECTED] -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
