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 variable name (e.g. static 'conf' structure in the mod_aspdotnet.cpp source) is horrid and needs to be cleaned up. I'm almost thinking, native_xx for variable names from apache and apr - would that improve legibility? Bill At 03:01 PM 11/18/2004, Jeff White wrote: >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: > >Parameter name = rv > Type=System.Int32 > Position=2 > Optional=False > >What does rv mean? > >ReturnValue, RequiredValue, >RequestedValue, RemovableVolume, >RottenVersion, RequiredValidation? > >So should _all_ Apache.Web variables be longer than "rr"? > >So the user can obtain from .NET what they mean like the below? > >Parameter name = msg > Type=System.String > Position=0 > Optional=False > >Message I assume, perhaps should be longer.... > >Parameter name = loglevel > Type=System.Int32 > Position=1 > Optional=False > >Some sort of Apache (or .NET) >log file level or value, I assume... > >At least, these two above examples give a user a chance to try to use them, >but rr and rv? > >Jeff
