Re: khttpd

Leonardo Marques de Souza (leo@opensystem.org.br)
Thu, 10 Jun 1999 17:22:21 +0000

> Why not give khttpd a devoted port? Why go to all these pains to dissect
> keep-alive connections and all that, when we can do <IMG
> SRC="http://my.server.net:81/banner.gif">? Is that just too easy for
> everyone? Is it because the benchmarks we were talking about would be able
> to use something like that?

I think... have a anyway to make the khttpd a port-tunnel?? like:

port[80]--[webserver]

when i run insmod khttp:

port[80]--[(80)khttpd]--[(80)webserver(apache)]

and ( dreamming more!)
run insmod khttp-module-perl

port[80] ---[(80)khttpd + perlmodule]---[(80)webserver]

All response in 80 port...
but khttpd run like a tunnel or filter betwen real port and webserver...

thats possible?

T+ (regards)

Leo

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/