From: "William A. Rowe, Jr."
let me get ahold of my life first
I see you doing so much, what life?
More later
Jeff
At 01:02 PM 11/22/2004, Jeff White wrote:
>From: "William A. Rowe, Jr."
>
>>One (extreme) hassle is leaving the httpd code legible to httpd'ers
>>and leaving .NET code legible to .NET'ers.
>>I had chosen the conventions of using 'traditional' variable names for httpd
>>datum, and 'wordy' variabl
From: "William A. Rowe, Jr."
One (extreme) hassle is leaving the
httpd code legible to httpd'ers
and leaving .NET code legible to .NET'ers.
I had chosen the conventions of using
'traditional' variable names for httpd datum,
and 'wordy' variable names for the internals of
Apache.Web.
In Apac
One (extreme) hassle is leaving the httpd code legible to httpd'ers
and leaving .NET code legible to .NET'ers.
I had chosen the conventions of using 'traditional' variable names
for httpd datum, and 'wordy' variable names for the internals of
Apache.Web.
There are quite a few cases where the vari
When looking at Apache.Web
member's parameters:
Parameter name = rr
Type=Apache.Native.request_rec*
Position=3
Optional=False
Here rr I assume means
request_rec
which I assume means request_record
(but just because of the type defined:
Type=Apache.Native.request_rec*).
But for others:
Par
