In driver thread you do not know how mahy and each pool you gonna use
until you call NsQueueConn, it is called for every ready socket untill
all queues are full, then you wait next iteration to start queuing
Zoran Vasiljevic wrote:
Am 08.01.2006 um 19:37 schrieb Vlad Seryakov:
There could be different connection pools with one connection queue
in each pool
Now if this is so, then I do not understand why NsQueueConn is not
called for each ready socket.
If the socket A is bound to conn pool A' and the socket B to conn pool B'
then there is no reason NOT to NsQueueConn(B) if the NsQueueConn(A) fails.
Or is there something deeper and not so obvious??
Cheers
Zoran
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log
files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
naviserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/naviserver-devel
--
Vlad Seryakov
571 262-8608 office
[EMAIL PROTECTED]
http://www.crystalballinc.com/vlad/
