Re: [Arianne-general] coding: removed support for building without threads

[Ulrich E. <Doo...@kn...>]

Monday 12 February 2001 21:47 AD, MIGUEL ANGEL BLANCH LARDIN wrote
< > I have removed all places in Core and CoreServer wher the
< > Network(Server-)Manager=B4s loop() function was explicitly called.
<
< This a bad decission, as I have get a few emails of problems with
< threads, and disabling threads make the app to work.
I can imagine where: the MessageManager and the Network[Server]Manager bo=
th=20
held pointers to a bunch of Queues. Pointers to these Queues were given o=
ut=20
freely.=20
I have changed this behaviour so that _only_ the MessageManager has these=
=20
Queues and a Mutex for each. When anyone wants a Queue, he only gets a=20
QueueProxy (new class). This thing works like the Templock-class (locking=
 and=20
unlocking the mutex) but has overloaded operator*() and operator->() to m=
ake=20
it 'feel' like a pointer to a Queue. (gonna make this a template someday =
=2E..)

I=B4m not giving up making this app multithreaded !

uli