Philipp von Weitershausen wrote:
Okay, how about the config parser registers the utility:
The config parser (ZConfig) is generic
Well, it runs of a schema which uses handlers specific to the project,
so I don't see what your point is here...
the component architecture. The main() program
Philipp von Weitershausen wrote:
What I meant: Since is we have things like zope.paste which work fine as
3rd party packages already, perhaps the Zope 3 core just needs to
*support* this separation of server configuration and application
definition, but doesn't necessarily need to *do* it.
On 6 Feb 2007, at 09:59 , Chris Withers wrote:
Why named? If only so you can register many of them, then I call
yagni. Like a unix file system, a zope instance should only have
one root :-)
Sure. But the use of named utilities would make it a tad easier
because you wouldn't need ZCML
Philipp von Weitershausen wrote:
Why would this be in zope.conf at all?
I would have thought just having a normal zcml setup for a single,
global IRootObjectFactory utility would be fine...
Well, actually, you can't register it through ZCML because ZCML knows
nothing about the ZODB.
Okay,
On 6 Feb 2007, at 15:41 , Chris Withers wrote:
Philipp von Weitershausen wrote:
Why would this be in zope.conf at all?
I would have thought just having a normal zcml setup for a
single, global IRootObjectFactory utility would be fine...
Well, actually, you can't register it through ZCML
Philipp von Weitershausen wrote:
Perhaps there's not a need for that separation in the Zope 3 core with
packages like zope.paste around...
Sorry, you lost me... there's what a need for what seperation?
I thik we can stick with ZConfig for now, even though Jim doesn't like
it... *wink* ;)
I
On 5 Feb 2007, at 11:50 , Chris Withers wrote:
Philipp von Weitershausen wrote:
Perhaps there's not a need for that separation in the Zope 3 core
with packages like zope.paste around...
Sorry, you lost me... there's what a need for what seperation?
What I meant: Since is we have things
On 2 Feb 2007, at 11:08 , Chris Withers wrote:
Philipp von Weitershausen wrote:
Chris Withers wrote:
Stephan Richter wrote:
On Thursday 01 February 2007 02:42, Chris Withers wrote:
Is there a non-twisted main.py of does zope.app.twisted.main
get used
for all Zope 3 instances?
Philipp von Weitershausen wrote:
As Jim pointed out in an earlier discussion [1], we would rather like to
separate server configuration from the application definition (ZODB,
logs, etc.).
That sounds like any work I do here will help...
- make twisted/zserver interchangeable through a
On 2 Feb 2007, at 18:15 , Chris Withers wrote:
Philipp von Weitershausen wrote:
As Jim pointed out in an earlier discussion [1], we would rather
like to separate server configuration from the application
definition (ZODB, logs, etc.).
That sounds like any work I do here will help...
-
Chris Withers wrote:
Stephan Richter wrote:
On Thursday 01 February 2007 02:42, Chris Withers wrote:
Is there a non-twisted main.py of does zope.app.twisted.main get used
for all Zope 3 instances?
zope.app.server.main
How do you switch between the two?
mkzopeinstance creates a twisted
Philipp von Weitershausen wrote:
Chris Withers wrote:
Stephan Richter wrote:
On Thursday 01 February 2007 02:42, Chris Withers wrote:
Is there a non-twisted main.py of does zope.app.twisted.main get used
for all Zope 3 instances?
zope.app.server.main
How do you switch between the two?
12 matches
Mail list logo
