httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From p.@sweng.stortek.com
Subject Re: OS/390 Translation
Date Fri, 03 Dec 1999 17:28:31 GMT
In a recent note, Martin Kraemer said:

> Date: Fri, 3 Dec 1999 18:11:26 +0100
> 
> On the socket level, we *ALWAYS* have to transmit '\012' and '\015'.
> 
> But changing '\012' to '\n' and '\015' to '\r' everywhere would break
> on ASCII based systems where  ('\n' != '\012') or ('\r' != '\015')
> (when it's an ASCII system, there's no implied additional conversion
> step which could fix the different representations. On EBCDIC, we
> have this translation step).
> 
> That is for instance the case with Macintosh and similar systems
> (where '\n' == '\015', like in OS-9/68k). The reason why explicit
> '\012' and  '\015' were coded in the first place was to avoid
> protocol errors caused by such a differing ASCII implementation.
> 
I just did a quick grep through the source code.  The preponderance
of the use of '\012' is in arguments to ap_rputs().  Would it be
a possible solution to add an ap_rputs_nl() function which would
append the platform-dependent newline to its argument then call
ap_rputs()?  (asked without even looking at what ap_rputs() does.)

-- gil
-- 
StorageTek
INFORMATION made POWERFUL

Mime
View raw message