Uri Guttman wrote: > BT> I'd then avoid writing all of the multi-process logic by > BT> using Apache for that piece... > > and what if you aren't using http for the clients? [...] > i really hate how apache (1 or 2) is being touted as the next great > application platform and savior.
There seems to be a trend towards using Apache as a generic multi-processing daemon, even for protocols unrelated to HTTP. One example of this is: http://search.cpan.org/~mock/Apache-SMTP-0.01/lib/Apache/SMTP.pm which implements an SMTP server in Apache via mod_perl. There are even native modules that implement non-HTTP protocols, such as mod_pop3: http://httpd.apache.org/modules/ (I could have sworn I ran across a (non-mod_perl) project implementing an SMTP server in Apache, but I can't seem to located it.) So the point you've made elsewhere in the thread about stateless HTTP not being a good fit for many projects isn't relevant to whether you use Apache. Whether it makes sense to use Apache as nothing more than a multi-processing daemon for a non-HTTP protocol is another matter. I don't think it's an approach I'd be inclined to take. -Tom -- Tom Metro Venture Logic, Newton, MA, USA "Enterprise solutions through open source." Professional Profile: https://www.linkedin.com/e/fps/3452158/ _______________________________________________ Boston-pm mailing list [email protected] http://mail.pm.org/mailman/listinfo/boston-pm
