On Sun, 23 Oct 2005, Adi Oanca wrote:
Ingo Weinhold wrote:[...]
BTW, since the number of messages in the looper port is actually no indicator of how busy the window thread is at the moment (only how busy it was since it last transferred the messages from the port to its message queue), it might be a good idea to let the app server know the number of messages in the queue (e.g. through shared memory), so that the server-side queue could also be used when the port is not full but there are too many messages in the client side message queue already.
I don't know... I don't think there's a strong reason for this...
The messages in the port queue are fetched after any message is processed, and the MessageQueue object does its job very good. If processing a message takes so long that the port queue gets filled up, that's an example of bad programming - user should use a specialised thread.