I know, I know -- total flame bait... But really, has anyone had any experience with the *other* open source Web Application Server, Enhydra? I just "discovered" it the other day while writing an introduction to Zope for my co-workers, as we're about to embark on a serious new development project. At any rate, after already being *highly* impressed and sold on Zope - I ended up spending a little time at www.enhydra.org and became more and more enthused. I'm currently downloading it to give it a fair chance - but I was wondering if anyone else here has happened to have already given it a review, and if so, could you relay some of your findings/opinions? I've yet to stumble across any mention of Enhydra in any of the Zope documentation/introductory material or even yet on this list. I'd be interested in hearing any testimonials from Zopistas. Thanks for any input! Beers, Corey
Flame bait? Catch this: I have recently been reaching the disillusionment phase with Zope, so please take it all with several grains of salt. I happened upon an article in the ArsDigital Systems Journal that I thought was a fairly neutral review of Enhydra. http://www.arsdigita.com/asj/enhydra/index.adp The more thought-provoking part of the article was a reference to a fairly disparaging view of application servers in general. http://www.arsdigita.com/asj/application-servers What got me to ArsDigita was AMK's Zope frustrations. http://www.amk.ca/python/writing/why-not-zope.html (BTW, some of these issuses are being addressed.) Which also lead me to Chuck Esterbrook's musings http://pywx.idyll.org/advocacy/why-not-zope.html http://pywx.idyll.org/advocacy/why-not-zope-2.html Chuck Esterbrook created webware as his answer to Zope's limitations and complexity. http://webware.sourceforge.net/ Titus Brown advocates use AOLserver and Python (instead of TCL) http://pywx.idyll.org/advocacy/ IBM developerworks has a couple of Enhydra articles (which I have not read yet) http://www-106.ibm.com/developerworks/library/enhydra.html http://www-106.ibm.com/developerworks/library/w-friend.html?dwzone=web In summary: Don't build what you don't need -- do the simplest thing that could possibly work. Evaluate potential solutions in terms of business value to YOUR customers, not in terms of market hype. HTH -- Terrel Shumway
on 12/29/00 9:52 PM, corey@axcelerant.com at corey@axcelerant.com wrote:
But really, has anyone had any experience with the *other* open source Web Application Server, Enhydra?
...
At any rate, after already being *highly* impressed and sold on Zope - I ended up spending a little time at www.enhydra.org and became more and more enthused.
Zope has the advantages of a well-developed security strategy that allows an orderly delegation of management of subtrees of a site, an application framework that supports things like acquisition, a built-in object database and a broader range of freely-available (with source) applications such as Squishdot and ZWiki (this could change, but so far I haven't found a comparable set of freely-available servlets). Because you can do a good bit of development directly through the web and most sub-developers do not need access to the file system of the host machine, Zope is suited to dynamic sites with multiple developers working on separate site subcomponents. Enhydra offers Sun's Java Servlet 2.2 API, which is becoming popular for web application development in business, and it theoretically can be used with Cocoon, a very interesting XML publishing system/application manager implemented as a servlet (xml.apache.org/cocoon). Enhydra can serve standard web pages from the file system as well as manage servlets and it offers several strategies for embedding dynamic content in pages. However, page and servlet developers must have access to the host file system to mount the pages and servlets, and the Enhydra administrator probably needs to manage the final configuration of each servlet (you must edit the server's configuration files and restart the server). This would seem to lend itself better to the creation of applications that are relatively static once they are put in place. One interesting aspect of servlets is that they can be written in JPython or its successor, Jython, rather than Java and then compiled to Java byte code directly. Thus you can write your application logic in Python and have access to both the Java and Python code libraries. There is a useful servlet available called 'PyServlet' by Stefano Mazzocchi that will load JPython servlets from source code, allowing the source code files to be edited after installation (they will re-load then). I haven't tested this under complex or high load conditions, but it works pretty well with simple servlets using Tomcat (jakarta.apache.org) as a servlet container. Enhydra would also be expected to support this and I think this capability should increase the interest of the python community in Enhydra and the other standard Java servlet containers. Jim Harrison Univ. of Pittsburgh
On Friday 29 December 2000, at 18 h 52, the keyboard of corey@axcelerant.com wrote:
But really, has anyone had any experience with the *other* open source Web Application Server, Enhydra?
Why, *the* other? There is only one? http://www.brics.dk/bigwig/
You may be interested to know that the HiperDOM project, currently in development by DC and my company, aims ot bring to Zope a template system similar to the XMLC of Enhydra. Check it out: http://www.zope.org/Members/mj/HiperDom In my opinion, you really can't compare Enhydra with Zope. Enhydra is exclusively a programmers tool. Zope, through it's friendly UI, enables you to delegate many maintenance activities to end-users, where they belong. Regards, Luciano Ramalho Hiperlogica Sao Paulo - Brazil
participants (5)
-
coreyï¼ axcelerant.com -
Jim Harrison -
Luciano Ramalho -
Stephane Bortzmeyer -
Terrel H. Shumway