Am 09.01.2006 um 17:27 schrieb Vlad Seryakov:
Usually it's only one default pool used.
Yes, that's why I'm not so sure that the change
would be that optimal. I guess I should make some
clarifying comment at that place and leave it as-is.
Zoran
Usually it's only one default pool used.
Zoran Vasiljevic wrote:
Am 09.01.2006 um 17:07 schrieb Zoran Vasiljevic:
Now, if nobody sees any problem with that, I will
make that change in driver.c
hmhmhmhm... one drawback is: if you only DO have just
one conn queue, then it is better the way
Am 09.01.2006 um 17:07 schrieb Zoran Vasiljevic:
Now, if nobody sees any problem with that, I will
make that change in driver.c
hmhmhmhm... one drawback is: if you only DO have just
one conn queue, then it is better the way it is now...
One could make NsQueueConn recognize that case and retur
Am 09.01.2006 um 16:38 schrieb Vlad Seryakov:
Looks like it will skip
(for the others: I had a short conversation
with Vlad over AIM double-checking this)
Yes, this is what I thought. So, the "proper"
way would be to code this like:
if (waitPtr != NULL) {
sockPtr = NULL;
Looks like it will skip
Zoran Vasiljevic wrote:
Am 09.01.2006 um 16:11 schrieb Vlad Seryakov:
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 st
Am 09.01.2006 um 16:11 schrieb Vlad Seryakov:
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
Say I have 10 ready sockets. 2 of t
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
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
p
There could be different connection pools with one connection queue in
each pool
Zoran Vasiljevic wrote:
Am 07.01.2006 um 17:37 schrieb Vlad Seryakov:
It means if cannot queue socket, does not make sense to queue others
because the only fail may happen in NsQueueConn is queue overflow, so
Am 07.01.2006 um 17:37 schrieb Vlad Seryakov:
It means if cannot queue socket, does not make sense to queue
others because the only fail may happen in NsQueueConn is queue
overflow, so need to wait until there are available slots.
How many connection queues are there? Do we have one connect
It means if cannot queue socket, does not make sense to queue others
because the only fail may happen in NsQueueConn is queue overflow, so
need to wait until there are available slots.
Zoran Vasiljevic wrote:
Hi,
I have some trouble understanding the code from driver.c
below. This is used in
Hi,
I have some trouble understanding the code from driver.c
below. This is used in both Driver and SpoolerThread code:
/*
* Attempt to queue any pending connection
* after reversing the list to ensure oldest
* connections are tried first.
*/
12 matches
Mail list logo
