I don't understand this statement. Zope AFAIK is a server-side-document-generator/CGI/servlet sort of thing. Quite a few people on the list use jython together with tomcat to generate web content, as I recall (or at least have asked questions about how to do so). So in what way is jython 'strictly client-side'?
Asked in genuine ignorance - not a challenge!
--- Terry wrote ---
>As far as I know (and I've been looking -- still am),
>there's no direct support for Jython in Zope. However,
>Jython is strictly a *client-side* technology and
>Zope is strictly *server-side* -- so in principle, there
>isn't much overlap.
>I was thinking of waiting until the O'Reilly book
>on Jython comes out (I'm not experienced at Java,
>so I don't think the other book is going to help
>me so much), and then having a go at writing such
>a product myself, since I want to do a fairly
>large amount of Jython stuff with Zope. My attraction
>to this is the beauty of having both server and
>client programmed in the same programming language
>(Python), instead of having to learn and interface
>between two different ones.
1. I think that what you imagine is doable
2. Honestly it is not clear to me how
much useful it would be.
Applets can be a useful tool depending
on the kind of work-distribution between
server and client you want to achieve,
and your deployment scenario.
For sure Jython applets are a bit more
heavy than pure Java ones, counting
the runtime or not.
3. Writing this would require a fair
amount of Java/Jython expertise,
especially because at least IMO
it would make sense only if there
is a high-level/smooth and meaningful
interface for talking back to the server,
And for this there are no standard pre-built
So much with ranting.
About our book,
[before having an unhappy reader]
we try to supply valuable information
to both audiences, Java-to-Jython
To the first audience Java-to-Jython
we teach Jython.
To the second audience [because of space
/market issues, and because there are already
a lot of books and material about Java around]
we supply comparative information
CPython/Jython and Java/Python but we
still expect that they will read/obtain
introductory Java information from other sources.
If someone comes from Python and have
just gone through some introduction to Java,
he will still have a lot of expections
about what he can do and how because
of the CPython background, we try to
offer valuable information for the cases
where those expections are going to become
gotchas or delusional. There are aspects
of Jython that unless you are a Java
and Python expert and have possibly
looked at the implementation can seem
just arbitrary [more on a different post].
I don't think there is a sensible and valuable
way to explain and teach Jython as
Python + an Extension-that-is-a-Python-view-on-
and then you are done with it.
Java is not simply a language, it is a platform
and rich library too.
regards, Samuele Pedroni.