Dakota Burns wrote:
Are their any downfalls to running Jetty versus Tomcat?
Nope, really just comes down to personal preference. The big thing I always hear about Jetty is that it's more "embeddable" and perhaps a bit more lightweight than Tomcat, but I've had good luck with Tomcat personally. Either one's a great choice.
It seems to me that Jetty is a lightweight java server, and ... if it does the job -- why not consider as an option for running "as service" with OpenBD in addition to the manual "Ready2Run" package, which is great, by the way?
The Ready2Run package is designed to give people an OpenBD bundle that works more like what they might be familiar with from using ColdFusion, but it's perfectly fine to use this in production if you like, meaning this isn't a stripped-down version of Jetty or anything like that, it's just been configured in a specific way so multiple contexts use the same OpenBD instance.
So you can use the Ready2Run version, or you can certainly grab Jetty and deploy OpenBD as a WAR yourself, which may give you a bit more flexibility depending on what you need to do with your server.
You can certainly run Jetty as a service, which on Linux really just means start it up when the machine boots. Looks like Jordan covered that really well in the email that came in while I was typing this. ;-)
-- Matt Woodward [email protected] http://www.mattwoodward.com/blog Please 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
