Tommi Mäkitalo <tommi@...> writes: > I wanted to suggest the proxy component. The C-API is also a good idea. > Another option is to implement a CGI component. I have thought about it, > but not enough to really do it. Maybe it would be interesting to have > CGI. Then you can also integrate perl or other scripts easily. The > performance will be bad as CGI needs to start a process for each > request, but just as an option for something it may be interesting. > > Tommi
Oh, FastCGI and scgi and wsgi would be much better, performance-wise. Lighttpd 1.5 have a unified proxy for different protocols which sounds interesting. But personally I think making the HTTP proxy reliable and asynchronous (so that it is not overwhelmes the thread pool when the proxied server is slow) should be the priority, as HTTP is the most general protocol nowadays. ------------------------------------------------------------------------------ LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d _______________________________________________ Tntnet-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tntnet-general
