You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@httpd.apache.org by Hongmiao <hw...@lab7networks.com> on 2003/02/15 21:20:50 UTC

[users@httpd] For Help

Hi,

I developed the LSP (Layer Service Provider) on Windows 2000, when client query big file through Apache server, there is a problems if my LSP intercept.

I check the apache code, apache server uses TransmitFile() function to transfer big file, and uses WaitForSingleObject(signal object is socket instead of event) to get signaled. My question is who will signal the apache server, what is the mechanism of this signaled system. If WaitForSingleObject() using event as signaled object, my LSP can signaled the apache server. But if WaitForSingleObject() used socket as signaled object, someone else can ahead my LSP inform the apache even the overlapped I/O transferred result is not updated.

Couldn't you tell me why apache server used socket as signaled object for WaitForSingleObject() function instead of event, and who will signal the overlapped I/O result? What's the mechanism for this signal system.

Thanks in advance.

Hongmiao Wang


RE: [users@httpd] For Help

Posted by Jeff Cohen <ap...@gej-it.com>.
Join the apache-devepment list, I guess they can help you better then us
man.

All the best,
Jeff Cohen

-----Original Message-----
From: Hongmiao [mailto:hwang@lab7networks.com] 
Sent: Saturday, February 15, 2003 3:21 PM
To: users@httpd.apache.org
Subject: [users@httpd] For Help

Hi,
 
I developed the LSP (Layer Service Provider) on Windows 2000, when client
query big file through Apache server, there is a problems if my LSP
intercept.
 
I check the apache code, apache server uses TransmitFile() function to
transfer big file, and uses WaitForSingleObject(signal object is socket
instead of event) to get signaled. My question is who will signal the apache
server, what is the mechanism of this signaled system. If
WaitForSingleObject() using event as signaled object, my LSP can signaled
the apache server. But if WaitForSingleObject() used socket as signaled
object, someone else can ahead my LSP inform the apache even the overlapped
I/O transferred result is not updated.
 
Couldn't you tell me why apache server used socket as signaled object for
WaitForSingleObject() function instead of event, and who will signal the
overlapped I/O result? What's the mechanism for this signal system.
 
Thanks in advance.
 
Hongmiao Wang
 
 


---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org