Hi, On Monday, Monday 02 December 2013 at 01:49, Tony Rietwyk wrote: > > In short: if you do not have the need to access every bit directly use an > > existing server implementation and an easier way to communicate with it. > > For example Apache has modules for the FCGI and SCGI protocols. In this > > case Apache handles the complexities of HTTP while you just have to > > handle a significantly simpler protocol. > > Or keep your existing QTCPServer based code. Then use Apache as the > front-end, and proxy to your backend server. Very straight-forward.
I have never tried such a setup, but it sounds like a great idea. Upon reading
the mod_proxy docu a bit I would recommend restricting the configuration as
far as possible, e.g. by forcing Apache to use HTTP 1.0 you avoid the two most
troublesome features (100-continue and chunked encoding).
Konrad
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
