WriteClient blocking other threads
sujeet
I'm a newbie to ISAPI
I was goining through the below link about writeclient blocking other
threads due to it's synchronous design .
http://support.microsoft.com/default.aspx?scid=kb;en-us;840875
The stack given in link is something like this
ChildEBP RetAddr
017af62c 77f43741 SharedUserData!SystemCallStub+0x4
017af630 67153781 ntdll!NtWaitForSingleObject+0xc
017af658 67151c61 httpapi!HttpApiSynchronousDeviceControl+0x57
017af67c 67152db0 httpapi!HttpApiDeviceControl+0x23
017af6cc 5a3616b7 httpapi!HttpSendResponseEntityBody+0x64
017af710 5a36170d w3dt!UL_NATIVE_REQUEST::SendEntity+0x7c
017af730 5a3944cd w3dt!UlAtqSendEntityBody+0x1d
017af75c 5a399987 w3core!SendEntityBodyAndLogDataHelper+0x7c
017af798 5a399a3a w3core!W3_RESPONSE::SendEntity+0xf1
017af7bc 5a39b38c w3core!W3_CONTEXT::SendEntity+0x8c
017af7d8 5a32378d w3core!ISAPI_REQUEST::WriteClient+0xf7
017afa3c 10016dfe w3isapi!WriteClient+0x27d
77e42f38 458b18ec
Can you please help me in debugging writeclient API , and get a
similar stack.
I'm using visual studio debugger , i do have my filter dll, which is
registered with the wspsrv( Firewall service ).
I have set breakpoints on writeclient API in my filter ,
What would be a ideal way ,
buffer up more data and send into larger chunks ?..
so we can have very less calls to writeclient and save network delay
of 70-200ms for every ACK..
what could be an ideal buffer size, or would it be permissible?..
Any help on this could be very help.
Thanks,
Sujeet