Am 07.01.2006 um 17:41 schrieb Vlad Seryakov:
Just in case for future encahncements, we may restrict spooling
queue and keep socks in waiting list in driver for timeout or
something else.
allright.
Just in case for future encahncements, we may restrict spooling queue
and keep socks in waiting list in driver for timeout or something else.
Zoran Vasiljevic wrote:
Am 06.01.2006 um 16:56 schrieb Vlad Seryakov:
I uploaded driver.c into SFE, it needs more testing because after my
last corre
Yes, it makes sense
Zoran Vasiljevic wrote:
Am 06.01.2006 um 19:00 schrieb Vlad Seryakov:
sockPtr will be queued into the connection queue for processing, it
may happen from driver thread or from spooler thread, works equally.
Hmhmhmhmhmhmhm...
The SOCK_SPOOL is only retured from SockRea
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
Am 06.01.2006 um 16:56 schrieb Vlad Seryakov:
I uploaded driver.c into SFE, it needs more testing because after
my last corrections and cleanups it seems i broke something.
What is the meaning of:
case SOCK_SPOOL:
if (!SockSpoolPush(sockPtr)) {
Am 07.01.2006 um 09:18 schrieb Zoran Vasiljevic:
if (sockPtr->drvPtr->opts & NS_DRIVER_ASYNC) {
n = SockRead(sockPtr, 1);
U, sorry, wrong part...
if (sockPtr->drvPtr->opts & NS_DRIVER_ASYNC) {
n = SockRead(sockPtr, 0
Am 06.01.2006 um 19:00 schrieb Vlad Seryakov:
sockPtr will be queued into the connection queue for processing, it
may happen from driver thread or from spooler thread, works equally.
Hmhmhmhmhmhmhm...
The SOCK_SPOOL is only retured from SockRead(). The SockRead()
is only attempted in the Dri
