Re: ssl.cc -> tunnel.cc and it's future refactoring

ssl.cc now renamed to tunnel.cc after giving refactoring a careful
thought..

ssl.cc (now tunnel.cc) should be refactored into two components

a) A tunnel component, providing plain tunneling client<->server. This
is the majority of the code and the purpose of this file.

b) A CONNECT proxy component, forwarding a CONNECT request to a peer
proxy and then entering tunnel mode on the connection. This should
probably go into http.cc as it should share all logics for header
processing etc, and only switch to tunnel mode when a 200 reply have
been received.

As a first step the functions in tunnel.cc will be renamed to tunnel*
and httpConnect* accordingly.

Regards
Henrik

Robert Collins wrote:

> > > better to copy the file, and cvs rm the old one. That way cvs -D still
> > > works correctly.
> >
> > I see no problem with leaving a copy in the Attic until we are
> > completely done with it and no longer want to hear about the old name
> > (which should be not too long after 3.0 is branched I suppose).
>
> Well, given that we went to the effort of preserving history, we should
> keep it indefinately IMO. Still, I don't really care - minor detail.
>
> > How you do this mirroring I do not care ;-)
> >
> > I assume your request is it that you want to have a chance to fix the
> > arch mirror before I go messing around with the file contents?
>
> Exactly. And that gap can be fairly small: as long as there are separate
> CVS transactions, I'm happy.
>
> --
> GPG key available at: <http://users.bigpond.net.au/robertc/keys.txt>.
>
> ------------------------------------------------------------------------
> Name: signature.asc
> signature.asc Type: application/pgp-signature
> Description: This is a digitally signed message part
Received on Sat Feb 08 2003 - 10:19:46 MST