- 可伸缩性(性能,集群) - 可维护性/可管理性 - 错误报告/日志记录 - 基于组件(EJBs) ) - 数据库连接和对象持久性 - 交易 - ... 全部其中一些是标准化的(作为J2EE的一部分)。 从理论上讲,您可以将J2EE应用程序移动到另一个供应商运行的不同的b $ b环境中。应用程序服务器没有 大汗淋漓。 写(快)CGI时你没有这些随便可用 申请;你必须自己实施所有这些。 - Irmen de JongHow does FastCGI compare against java Apps running in java app serverslike TomCat, Sun One, WebLogic and WebSphere? Is there a business casefor switching from CGI to Java? Performance? Productivity? Features?Object orientation? Code Reuse?Any opinions? 解决方案Lots but I''m trying to stay objective! :-)Bottom line is: Does what you do now work for you? If so, don''tfix what''s not broken...Alan G. Nope, you can do that in Perl and certainly in Python (or Ruby).Or Tcl with an extension like [Incr Tcl]. Bottom line is: Does what you do now work for you? If so, don''t fix what''s not broken...Excellent suggestion.--David N. WeltonConsulting: http://www.dedasys.com/Personal: http://www.dedasys.com/davidw/Free Software: http://www.dedasys.com/freesoftware/Apache Tcl: http://tcl.apache.org/A (fast)CGI program compared to the actual Java program may not bemuch of a difference, depending on the program of course. What isa *huge* difference is that the Java app is running inside an*application server*. A (J2EE) Application Server provides arich environment on which to base your scalable enterprise applications:- security- connectivity- scalability (performance, clustering)- maintainability / managability- error reporting/logging- component based (EJBs)- database connectivity and object persistence- transactions- ...All of these are standardized in some way (as part of J2EE).In theory you can move your J2EE application to a differentenvironment running on a different vendor''s app server withoutmuch sweat.You don''t have any of this readily available when writing (fast)CGIapplications; you have to implement all of these yourself.--Irmen de Jong 这篇关于快速CGI与Jav​​a应用程序服务器的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持! 上岸,阿里云!
08-29 04:53