Mike O'Leary wrote:
Thanks for the info. I assume that ap_rwrite is writing directly to the
client which you mention is bad. What is the preferred method and why is
the ap_rwrite not preferred? Pardon me, I'm a newb.
Again, this is assuming you are writing an Apache 2 module.
Mike O'Leary wrote:
I was just wondering if the ap_rwrite call could return some value less than the
number of bytes requested to be written. I wanted to know if I need to put
a loop around all of my ap_rwrite calls to verify that all the data is
sent.
Mike,
In answer to your question, y
Samuel,
Thanks for taking the time to respond. My question was more about how the
Apache socket API works. I'm actually not experiencing any problems. I was
just wondering if the ap_rwrite call could return some value less than the
number of bytes requested to be written. I wanted to kn
On Mon, 15 Oct 2007 10:05:17 +0200
[EMAIL PROTECTED] wrote:
> I am writing a module for Apache 2.0.59 that works like a proxy to
> expose a Dime Soap Web service over classical HTTP
>
> The problem is when i send the content to the client, if the client
> closes the connection or pauses the d
Hello,
I am writing a module for Apache 2.0.59 that works like a proxy to
expose a Dime Soap Web service over classical HTTP
The problem is when i send the content to the client, if the client
closes the connection or pauses the download, i have to wait the
timeout to detect the problem
