Hi, Another layer of indirection/abstraction solves every problem in computier science. Every abstraction leaks, of course, but even with that consideration the solution is often much better.
I accept AMB's choice to stick to ANSI C, it has its advantages. But it may be sufficient when only the plain HTTP/1.0+spooling "wwwoffles" core would be written in C. There'd be another layer for HTTP/1.1 extensions like chunking, pipelining, .... On top would be size limits, process management, configuration, etc (features most complained about)... They could be then much more easily and flexibly managed using Python or something like. Maybe I'll try it someday. Let not the fear from "adding the another layer of complexity" prevent us thinking about better solution. Some problems are in principle impossible to solve on client side only, there comes ziproxy to save the day. If you didn't run into such problems, then don't need ziproxy, of course. Juraj > J> http://ziproxy.sourceforge.net/ > > another layer of complexity just when I'm running out of cells upstairs
