I have some experience working with: Oracle 8i J2EE Vignette StoryServer SAP ASP.NET Tomcat/Turbine/Velocity Avalon
all enable the creation of complex server applications. All have flaws and virtues. question: what does the perfect enterprise server framework look like? let's start with requirements...I guess it... - has a Database (like AvalonDB - http://cvs.apache.org/viewcvs/jakarta-avalon-cornerstone/apps/db/) - employs MVC (pull MVC - http://jakarta.apache.org/turbine/turbine-2/pullmodel.html) - follows Inversion of Control ( http://jakarta.apache.org/avalon/framework/inversion-of-control.html) - is Event-based (like SEDA - http://www.cs.berkeley.edu/~mdw/proj/sandstorm/) - is Component-based(COP/SOP - http://jakarta.apache.org/avalon/developing/introduction.html) - allows hot-(re)deploy (Tomcat Manager - http://jakarta.apache.org/tomcat/tomcat-4.0-doc/manager-howto.html) - is manageable (JMX Impl - http://cvs.apache.org/viewcvs/jakarta-avalon-phoenix/src/java/org/apache/jmx /) - supports transactions (JTA - http://jakarta.apache.org/slide/javadoc/org/apache/slide/transaction/package -summary.html) - has a template engine (Velocity - http://jakarta.apache.org/velocity/index.html) - includes a webserver (Apache - http://httpd.apache.org) Besides that, it needs to be scalable, stable, portable, secure, etc. But what architecture does that lead to? takers? - Leo Simons -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
