[omniORB-dev] Reason for omniORB imposed latency when handling multiplexed requests on a server connection?

[Jonathan Biggar]

I've noticed that giopServer::notifyWkPreUpCall always calls 
setSelectable with now = 0.  This means that the select loop is not 
immediately notified that the server connection is readable.  Since the 
main select loop has a fixed wakeup timeout of 50ms, up to that amount 
of latency is seen before a second request on the same server connection 
is recognized and processed.

Is there a particular design reason for this added latency?  Otherwise 
I'm strongly tempted to change notifyWkPreUpCall to set now = 1 and get 
immediate service for the connection.

-- 
Jon Biggar
Levanta
jon at levanta.com