On 9/18/06, Vlad Seryakov <[EMAIL PROTECTED]> wrote:
It started as small proxy to handle special cases when we need access to
private LAN inside our LAN to provision some servers via WEB. I never
intended to make it full HTTP proxy but even in current state it does
work and we access our appliance boxes though this module.
To make it more usefull, it needs to be in separate module, i agree.
Currently it uses internal proxy which is in the core, that's why
specific register by protocol method, this is how it defined and used in
the op.c and used in queue.c.
Not sure about transparent proxy on Tcl level, this needs a lot of code
it is more like proxy driver as i see it.
Well, no. You could transparent proxy right now by using
ns_register_proc and ns_http to forward the request. It's *less*
code.
There's two separate issues: where the HTTP proxy code lives; and how
it is activated. The only think stopping you moving the code to the
nsproxy module -- which is the right thing to do even if you don't
plan to immediately add more to the simple implementation you have now
-- is the naming clash with Zoran's bundled nsproxy module. The
activation stuff I guess needs some thought.
Exposing this as Tcl commands is definitely a good move. But with the
activation bug and naming confusion it's sort of going in the wrong
direction. It would be great to set things off on the right foot so
that people could more easily contribute.
