This is starting to turn into a CF discussion versus a feature set discussion. Scalability is proven with the J2EE technology. It is solid, versatile, and many open projects are available for your contributions. Commercial product support is also available. The user community seems very good at helping others in distress. The comments made regarding being an MS shop are valid and if that's your thing, well...good luck. Other comments regarding choosing the technology for the type of solution you are trying to provide are valid as well. Don't be shortsighted though. The needs of today should be weighed with what you can best decide you'll need tomorrow; porting is way more expensive than selecting the right platform the first time. The other solutions discussed in this thread fall short (IMHO) in terms of flexibility for the future.
As was already mentioned, one huge advantage of Tomcat and web apps over the other technologies is the SecurityManager. I'm not saying it's the easiest thing to use, but it lets you lock down access to your app server, web apps, database connections, socket connections, and supporting files. The other products mentioned so far in this thread favor features and security by abstraction. That's unfortunate, because the same managers and developers that didn't consider security bite the bullet when their services are compromised. I wouldn't want a product manager's job, because if I had to defend time to market vs. security/flexibility, the latter wins hands down every time. My bonus check probably wouldn't show up, but I could have peace of mind. Regards, Garrel Renick -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
