cvs commit: apache-site/contributors index.html
martin 98/11/19 07:57:53 Modified:contributors index.html Log: My company is called Siemens now (no longer Siemens Nixdorf) Revision ChangesPath 1.54 +1 -1 apache-site/contributors/index.html Index: index.html === RCS file: /export/home/cvs/apache-site/contributors/index.html,v retrieving revision 1.53 retrieving revision 1.54 diff -u -r1.53 -r1.54 --- index.html1998/10/30 02:16:08 1.53 +++ index.html1998/11/19 15:57:52 1.54 @@ -325,7 +325,7 @@ STRONGName:/STRONG A NAME=kraemerMartin Kraemer/ABR STRONGEmail:/STRONG Martin.Kraemer#64;mch.sni.deBR -STRONGOrganization:/STRONG Siemens Nixdorf Information Systems AGBR +STRONGOrganization:/STRONG Siemens AGBR STRONGOccupation:/STRONG Software Development EngineerBR STRONGLocation:/STRONG Munich, GermanyBR STRONGComments:/STRONG I like portable code that's easily understood.BR
cvs commit: apache-1.3/src/support apxs.pl
rse 98/11/19 08:41:16 Modified:src/support apxs.pl Log: Bring the `apxs -g -n foo' generated mod_foo.c in sync with current state of include files. Revision ChangesPath 1.12 +2 -1 apache-1.3/src/support/apxs.pl Index: apxs.pl === RCS file: /export/home/cvs/apache-1.3/src/support/apxs.pl,v retrieving revision 1.11 retrieving revision 1.12 diff -u -r1.11 -r1.12 --- apxs.pl 1998/10/28 15:01:17 1.11 +++ apxs.pl 1998/11/19 16:41:12 1.12 @@ -568,7 +568,8 @@ #include httpd.h #include http_config.h -#include conf.h +#include http_protocol.h +#include ap_config.h /* The sample content handler */ static int %NAME%_handler(request_rec *r)
cvs commit: apache-2.0/docs some_reasons_for_layered_io
dirkx 98/11/19 08:50:54 Added: docs some_reasons_for_layered_io Log: mumble mumble Revision ChangesPath 1.1 apache-2.0/docs/some_reasons_for_layered_io Index: some_reasons_for_layered_io === This file is there so that I do not have to remind myself about the reasons for Layered IO, apart from the obvious one. 0. To get away from a 1 to 1 mapping i.e. a single URI can cause multiple backend requests, in arbitrary configurations, such as in paralel, tunnel/piped, or in some sort of funnel mode. Such multiple backend requests, with fully layered IO can be treated exactly like any URI request; and recursion is born :-) 1. To do on the fly charset conversion Be, theoretically, be able to send out your content using latin1, latin2 or any other charset; generated from static _and_ dynamic content in other charsets (typically unicode encoded as UTF7 or UTF8). Such conversion is prompted by things like the user-agent string, a cookie, or other hints about the capabilities of the OS, language preferences and other (in)capabilities of the final receipient. 2. To be able to do fancy templates Have your application/cgi sending out an XML structure of field/value pair-ed contents; which is substituted into a template by the web server; possibly based on information accessible/known to the webserver which you do not want to be known to the backend script. Ideally that template would be just as easy to generate by a backend as well (see 0). 3. On the fly translation And other general text and output mungling, such as translating an english page in spanish whilst it goes through your Proxy, or JPEG-ing a GIF generated by mod_perl+gd. Dw.
cvs commit: apache-1.3 STATUS
dougm 98/11/19 09:46:41 Modified:.STATUS Log: un-static-ize ap_exists_config_define? Revision ChangesPath 1.542 +4 -0 apache-1.3/STATUS Index: STATUS === RCS file: /export/home/cvs/apache-1.3/STATUS,v retrieving revision 1.541 retrieving revision 1.542 diff -u -r1.541 -r1.542 --- STATUS1998/11/15 18:32:25 1.541 +++ STATUS1998/11/19 17:46:40 1.542 @@ -318,6 +318,10 @@ PR #1120 Brian: +1 +* un-static-ize ap_exists_config_define() in http_core.c for + everybody to use + Doug: +1 + Win32 specific issues: Important
