Re: [Jython-dev] Jython 2.1a3 on j2sdk1.4.0beta

[Titus B. <ti...@ca...>]

->   TB> that Zope's C code is primarily in the area of medusa, their
->   TB> request-handling front-end.  So, if you can figure out how to
->   TB> disentangle Zope from medusa, it shouldn't be too hard to whip
->   TB> up something that works.
-> 
-> There is little or no C code in medusa.  A quick scan of the Zope
-> source tree shows that C code is used in the following places:

Really?  Oh, because asyncore has been integrated into the distribution,
right?  But it's not in Jython... for obvious reasons.

->     - ExtensionClass and friends, which are used to implement
->       acquisition and a host of other things;

Ahh, this I didn't know about...

->     - BTrees, which are used to implement catalogs aka searches; and

Presumably this functionality could be replaced fairly easily with
existing Java classes, no?

->     - ZODB, which provides the persistence / transaction machinery.

ZODB is (AFAIK) client/server, yes?

-> There is also C code in access control, document templates, and the
-> PCGI wrapper.  Zope also includes zlib and expat, which are
-> implemented in C.

Wow.  For zlib and expat, there are drop-in replacements; dunno how hard
the rest would be.

->   TB> Also see my "Zope is Evil" page for mild commentary about the
->   TB> smugness of Zopatistas ;).
-> 
-> I'm sure you have plenty of legitimate technical criticisms of Zope.
-> "Evil" doesn't suggest to me what they are.  It sounds more like name
-> calling to me, but perhaps I'm just smug.

;) You should probably go read the page... Most of my criticisms are not,
in fact, technical, but (at least wrt the state of documentation and the
user community) were methodological.

--t