"Marcus Overhagen" <ml@xxxxxxxxxxxx> wrote: > Limitations of the current BeOS and also the NewOS or OpenBeOS kernel > prevent the use of a Simple WaitForMultipleObjects() call to wait on > a number of ports at the same time. That's the reason why one thread > for each connection port is created on the app_server side. > > The best solution would be to create a WaitForMultipleObjects() > function, > however, this would involve very huge changes to the kernel, and will > not be done for R1. I am not sure if I touch the whole message with this, but is there any need that any window/bitmap need to have more than a single port to communicate with? Can't we just have the ID (i.e. the reply-to-port) send as part of the message? Then we would just need to start i.e. 1 thread per CPU on the server side which collect the message and handle it? Apart from that, the only thing I don't like that much from your solution is that the event array has to be scanned for every message that is written. That could slow down the whole thing considerably, I guess. Adios... Axel.