Hi all:
I've been reading an article from Bruce Eckel named "The departure of
the
hyper-enthusiasts" (http://www.artima.com/weblogs/viewpost.jsp?thread=141312),
and in a paragraph, I read the next:
My own experience in web frameworks was with Zope. In an interesting
parallel with EJB3, Zope
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Dimitry,
you introduced the password managers. In
\src\zope\app\server\mkzopeinstance.py
the admin can choose the password manager. The statement is
> password_manager = self.read_input_line(
> "Password Manager Number [1]: ")
Egon Frerich wrote:
Hello Dimitry,
you introduced the password managers. In
\src\zope\app\server\mkzopeinstance.py
the admin can choose the password manager. The statement is
password_manager = self.read_input_line(
"Password Manager Number [1]: ")
(line 188)
I assume " [1]"
On Friday 23 December 2005 04:48, Antonio Beamud Montero wrote:
> IMHO, he's rigth,
I think he is too, but his use case is narrow and about 180 degrees different.
Zope 3 tries to solve large problems, not small ones. The problem is that
noone has stepped up yet to make simple scripting easier.
Along the lines of "simple scripting", maybe something like
ArchGenXML/AGX for Zope 2. It goes from a UML model to a generated
product folder on the filesystem.
http://plone.org/documentation/tutorial/archgenxml-getting-started
I found the ideas in this concept language disturbing:
http://subtex
Tres Seaver wrote:
...
Ob. note: the performance characteristics of such servers (including
twisted) are not well understood in the context of Zope, until some
brave soul actually rolls out a high-volume production site and reports
success or failure.
I still agree with this. But I think it's
I've been working on trying to clean up the IResult/response.write mess.
I want to retract IResult from the public API.
Here's what I propose to do:
- Move IResult from zope.publisher.interfaces.http to
zope.publisher.http, thus making it a private interface.
- I'm arranging that a published
