Re: [Jython-users] JythonServlet over Java Servlet

[Michel P. <mi...@di...>]

> 3. With the combination of XMLC, it can achieve even better 
code/markup
> separation than model two JSP (taglib)! Think about it, do you
prefer
> logic/iteration tags in the markup, or python for loop and list
> comprehension?

I will be making an alpha release soon of Zope Page Templates for 
Jython.  For those of you who don't know, ZPTs are like XMLC except 
that they are much more "pythonic" and dynamic (the core PT engine 
was written by Guido and others at Pythonlabs and ZC).  I'm just 
chasing down one bug right now and then I'll share; hopefully ZC will 
include my patches in their Page Templates so I don't have to maintain

a fork.

> optimize the performance critical part in Java. I often wonder why
Jython
> Servlet hasn't caught on - IMO it's mainly because the developer 
need to
> understand 1) Java 2)Java servlet 3) Python, and realize the 
advantage of
> this combination.

A big problem, I think, is that the servlet API is very low level;
when 
Python programmers want something high level where they can just 
plug simple components into a framework and see those components 
added to their website.  The Servlet API is much to low-level to do
that; 
servlets programmers need to  worry about protcol details and other 
HTTP stuff.

Zope is kind of like this for CPython programmers, but it's not very 
simple.  Writing Zope extensions requires quite a bit of knowledge 
about Zope-only details.  Zope tries to abstract the protocol (read
"CGI") 
primarily with a mechanism called "object publishing".  An object 
publisher servlet would be pretty easy to write, and it may even be 
possible to use the old Zope kernel "bobo" to do the publishing work 
and just wrap it in a servlet.

-Michel