> In a message dated 01-03-31 14:11:19 EST, Ryan writes.
>
> > Not only is buff.c gone, but as Bill Stoddard has pointed out on
> > new-httpd, the modifications to Buff.c for 1.3 were minimal, it is not a
> > full re-write.
> >
> > Ryan
>
> As long as the conn->proxy thing is the 'other' side of the conversation
> and not a dupe of the client it shouldn't matter and my concerns are
> moot. The IBMHTTP conn_rec is still removing some of the WIN32 stuff,
> though, isn't it?
Ryan wouldn't know.
>
> My real point was that if new conn_rec(s) of any description are appearing
> somewhere in standard Apache then there is more chance for breakage in
> IBMHTTPD because their conn_rec is not the same. If a module is written to
> reference things that are missing from conn_rec under IBMHTTPD
> then that module is going to need 'ifdef IBMHTTPD' stuff in it and
> will need to know what is missing and why.
You will -never- see #ifdef IBMHTTPD (et. al) in Apache.
> It hasn't really been an issue so far except for a few transport
> layer modules I know of... but it could be.
>
> If the changes to conn_rec for IBM_HTTPD are trivial then why
> not get them posted up as a patch for the real Apache conn_rec so
> there is no mystery for module writers and the chance they
> might refer to things that aren't going to be there for IBMHTTPD
> compile of Apache?
I think I answered this already. I'll answer again... The changes are related to SSL
and
interfacing to the AFPA cache on Windows NT. The AFPA cache on Windows implements
it's own network
i/o layer (semantically similar to sockets). Thus, the field to hold a socket must be
able to hold
an AFPA socket. It is suckage related to not having access to the AFD (implements
sockets) source
code. Answering your question... the code would not be committed to the Apache tree
even if I made
it available. As a policy, the ASF does not commit code that is product specific (and
this is a damn
good policy IMHO).
Apache 2.0 architecture will allow us to handle the AFPA sockets much more cleanly. At
any rate,
only AS/400 has released an Apache 2.0 based product to date (based on apache 2.0
alpha 5) and it is
a technology preview only. IBM will not be releasing any other Apache 2.0 based
products for a
while, so it is way premature to begin questioning Apache 2.0 design decisions.
I suppose you want to get mod_gzip working on IHS? If you keep this off topic
discussion off the
mailing list maybe I can help you.
Bill