Eric Dawson wrote:
Are there any advantages/disadvantages to dropping IIS and just using Jetty on port 80?
Yes. ;-)
Should I drop IIS and use Apache?
You'll hear multiple opinions on this I'm sure, but the critieria I always use is if you don't need the functionality that a web server such as IIS or Apache offers, you can eliminate some complexity and redundancy of configuration by using the web server of the servlet container as your public web server.
So if all you're running is OpenBD (and other Java stuff) and you've read up on how Jetty works as a web server, and you feel comfortable with how Jetty's web server works, then I'd say this is definitely worth considering.
If, on the other hand, you're familiar with a particular web server and need to run things other than just OpenBD/Java, then you might still want to have a web server in front of Jetty. A common example is if people have virtual hosts on a server that won't be using Java/OpenBD, or if you need to run both OpenBD and PHP on the same server, etc. In that case you'd want to have a web server like Apache.
At the end of the day it really depends on your needs and what you're looking to accomplish. Short answer is if you don't feel you need something like Apache and it's just going to wind up being extra work, then using Jetty as the web server can be a bit simpler setup.
-- Matt Woodward [email protected] http://www.mattwoodward.com/blogPlease do not send me proprietary file formats such as Word, PowerPoint, etc. as attachments.
http://www.gnu.org/philosophy/no-word-attachments.html
smime.p7s
Description: S/MIME Cryptographic Signature
