Re: [users@httpd] Architecture recommendations, tips, hints and help

Am 29.11.2015 um 23:00 schrieb Nick Kew: On Sun, 2015-11-29 at 10:05 -0500, Yehuda Katz wrote: You might want to use CGI or FastCGI rather than an Apache module. You can write CGI in any language, including C or C++ and there are libraries that already implement FastCGI for both languages. There

Re: [users@httpd] Architecture recommendations, tips, hints and help

On Sun, 2015-11-29 at 10:05 -0500, Yehuda Katz wrote: > You might want to use CGI or FastCGI rather than an Apache module. You > can write CGI in any language, including C or C++ and there are > libraries that already implement FastCGI for both languages. > There are a few benefits of not using a m

Re: [users@httpd] Architecture recommendations, tips, hints and help

since this is not a very good architecture from several point of views It would be helpful if you name these explicitly. While it is well known that adding another level of indirection can solve any problem, it is good to know what a problem is. In any case, I also think CGI/WSGI/FCGI/HTTP

Re: [users@httpd] Architecture recommendations, tips, hints and help

You might want to use CGI or FastCGI rather than an Apache module. You can write CGI in any language, including C or C++ and there are libraries that already implement FastCGI for both languages. There are a few benefits of not using a module - If you update Apache, you may need to make changes to

[users@httpd] Architecture recommendations, tips, hints and help

Dear list, I'm faced with the following "architecture" of an application: - Linux Server (small VM) with MySQL-DB, accessible via SSL from outside of the server, access is limited to a set of users - Client is a .NET-Application connecting to the DB with one user for each installation since t