History for ZopeVsEnhydra

??changed:
-
<dtml-comment>
george runyan
in effort to summarize Enhydra vs. ZOPE for RAD development process.



</dtml-comment>
last updated: &dtml-bobobase_modification_time;<br>
first draft/idea: 5/1/00<br>
-------------------------------------------------<br>


    * <a href="http://www.zope.org/">zope</a>

    * <a href="http://www.enhydra.org/">enhydra</a>

Criteria:

    * obvious points (language, structure)

        * ZOPE

            * python scripting language w/ speed critical pieces in c

            * 100% opensource
 
            * community size (as of publish)

            * replacements of CGI by framework

            * project age: x years / src code base: y years

        * Enhydra

            * servlet framework for easily deployment and abstract data from presentation (?)

            * soon-to-be EJB J2EE compliant (?) w/ Bullsoft

            * 100% opensource (?)

            * project age: x years / src code base: y years

    * ease of use and speed to producitivity

        * ZOPE

        * Enhydra

    * 3rd party tools

        * ZOPE

        * Enhydra

    * debugging interface/structure
        
        * ZOPE
        
            * pdb - python debugger

            * medusa_monitor.py (monitor port)
 
            * tracebacks

        * Enhydra
   
            * borland J Builder

            * administrative console


    * out-of-the-box functionality (2?)

        * ZOPE

        * Enhydra


    * specifics: ACQUISITION vs cXML (dtml templating vs this as well)
        
        * through-the-web-interface

        * <a href="http://yyy.zope.org/Members/jpenny/variable_length_forms">trinkets</a>
 
        * seperation of content from application layer
 
            * XSLT/XML

            * cXML

            * DTML vs py/ext Methods


    * integration into EJB, D/COM(+), CORBA, XMLRPC/SOAP, general libraries (obvious points?)
         
         * LDAP

         * Oracle/MySQL/DB native authentication

         * /etc and NT domain

         * generic user authentication mechanisms (for future build-ons)