[Zope3-Users] Re: [Zope-dev] Zope 3 on Jython - Google Summer of Code

Martijn Faassen faassen at startifact.com
Fri Mar 28 11:05:06 EDT 2008


Hey,

Thanks for the feedback, Jim!

On Fri, Mar 28, 2008 at 3:06 PM, Jim Fulton <jim at zope.com> wrote:
[snip]
>
>  Some high-level comments:
>
>  - I suggest making porting C speed-ups a very low (non-existent)
>  priority.
>
>  - I expect security proxies to be one of the greatest challenges.
>  Maybe you can make them a low-priority by focussing initially on Zope
>  3 applications that don't use them, like grok.

+1 - I already mentioned this option as well. Note that existing Zope
3 applications can at least be made to run if you just let the
proxying code do nothing and return the object itself, I imagine.
They'll run insecurity, but they should run.

>  - I'd be inclined to take a bottom-up approach.  So, rather than
>  trying to get the Zope 3 "application" (a.k.a. Zope-management
>  interface, a.k.a Rotterdam skin, a.k.a zope.app.zcmlfiles) working,
>  focus instead on zope.interface, zope.component, and zope.publisher.
>  (Notice I didn't mention ZODB. :)
>
>  Are there wsgi servers for jython?

I think the Jython people already mentioned one, if I recall correctly.

I agree the focus should be on the lower-level packages. Note that
zope.interface was already ported at least some distance by the
twisted people at Pycon. I could therefore *imagine* focusing on some
speedup work by rewriting bits of code to Java, but I agree with you
that the primary, initial goal should be to get things to work, and
that performance work should be secondary. So perhaps this can be in
an 'optional-if-there-is-time-left' section, and going in with the
assumption that time will not be left.

Georgy, I suggest you go through my earlier comments again, and also
include Jim's comments (which are in agreement on most topics) and
work those into your proposal.

Regards,

Martijn

P.S. Note to interested by-standards, we're planning that Georgy is
going to be mentored primarily by the Jython people and as part of the
Jython summer of code project, not the Zope one. We are looking for a
good backup mentor who can assist on Zope-specific matters, though.


More information about the Zope-Dev mailing list