Hi Woodchuck, Am Mittwoch, 18. Mai 2005 21:46 schrieb Woodchuck: > another (simple) way to think about the difference is that Apache > serves static web pages, whereas Tomcat *can* do some server-side > processing and serve dynamic web pages. > > all else being equal (and with no mods installed on Apache such as > CGI/SSI/PHP), everyone visiting an Apache hosted website will see > exactly the same set of web pages. > > in contrast, a Tomcat hosted website *can* display different content > for the same requested web page for each visitor. > > you can use Tomcat to host totally static websites and not use Apache > if you wanted to. but Tomcat is meant for dynamic websites that > interact in some way with the user (ie. capture and process user > information) to produce custom results.
You are aware, that Apache can do the same as Tomcat. The only difference is that it will use PHP or Perl for doing this. You can run totally dynamic php websites with Apache and they can be as scalable and performant as JSP websites. I.e. PHP provides caching technologies which are very simple but at the same time close to static page performance. It only depends on your programming capabilities and your understanding of how the technology you are using ist working. You can write non-scalable and unperformant applications with both, PHP and Java. And if you try to programme PHP like Java or the other way round, yo will very likely not get the best results. So, the real difference between Tomcat and Apache - in my eyes - is not what each of them can do but how heydo it. The technology makes the difference. It is a decision between two different worlds and philosophies. I like both. Both have there strengthes. Best wishes Lutz --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
