Philipp von Weitershausen wrote:
Utilities are never created when they're looked up. They're created when
registered. Singletons (instances) are registered with the utility
registry, never factories.
Ah, yes, of course, I think I'm looking for local utilities...
and all I'm then doing with
Hi,
On Mon, Sep 18, 2006 at 03:37:28PM +0100, John Smith wrote:
Hi everyone!
the class
zope.app.publisher.browser.fileresource.FileResource
inherits from BrowserView and Resource in that order.
As far as I can work out, the __init__ method in
Resource
Philipp von Weitershausen wrote:
Chris Withers wrote:
Philipp von Weitershausen wrote:
Utilities are never created when they're looked up. They're created
when registered. Singletons (instances) are registered with the
utility registry, never factories.
Ah, yes, of course, I think I'm
Chris Withers wrote:
Hmm, okay, how have the UI's for the creation of local utilities been
built? (I'm thinking there must be some kind of drop-down somewhere
with an Add list as in Zope 2's ZMI, and that must include the
available types of local utility?)
Sure. Just use the standard Add
Hi All,
Curious about security in Zope 3.
In Zope 2 the following would be bad:
class X(SimpleItem): pass
class Y(SimpleItem): pass
class Z(SimpleItem): pass
x = X()
y = Y()
z = Z()
x.y = y
x.z = z
y.z = z
...because z has two containment paths:
x.z
x.y.z
...which might have different
Hi,
On Tue, Sep 19, 2006 at 04:53:45AM -0400, Stephan Richter wrote:
On Tuesday 19 September 2006 03:47, FB wrote:
(Please correct me if I'm wrong, I'm not a Python guru :-) )
[snip]
class Join(First, Second):
... def __init__(self):
... print 'init 3-before'
...
On Tuesday 19 September 2006 03:47, FB wrote:
(Please correct me if I'm wrong, I'm not a Python guru :-) )
Whenever you inherit from two classes, only the first class'
__init__ method is called implicitely on create of a new instance.
class First(object):
... def __init__(self):
...
On 9/19/06, Chris Withers [EMAIL PROTECTED] wrote:
...because z has two containment paths:
x.z
x.y.z
...which might have different security constraints.
How does Zope 3 handle the same kind of setup?
In Zope2 containment is looked up through acquisition, that is,
implicitly. In Zope3 it is
Martijn Pieters wrote:
On 9/19/06, Chris Withers
[EMAIL PROTECTED] wrote:
...because z has two containment paths:
x.z
x.y.z
...which might have different security constraints.
How does Zope 3 handle the same kind of setup?
In Zope2 containment is looked up through acquisition, that is,
Hi,
both Resource and BrowserView have a common parent
class, viz Location, whose parent class is object.
object
|
|
Location
/ \
/ \
/ \
BrowserView Resource
\/
\ /
Good news. I believe I found a way to do NTLM 4-way handshake with
zope3 and using PAU's plugin. But I need to modify zope3's http server
a little bit, to let zope3 support HTTP/1.1 persistent connection.
Currently I can
1. send NTLM challenge
2. receive NTLM type-1 message
3. send NTLM type-2
Hello:
I'd appreciate your comments on the issue shown below which happens on
Fedora Core 5, stock python 2.4.3 (with python-devel 2.4.3 installed)
and Zope 3.2.1.
[EMAIL PROTECTED] Zope-3.2.1]$ ./configure --prefix /usr/local/Zope-3.2.1
--force --with-python /usr/bin/python2.4
Configuring Zope
I know I read about this error somewhere before, but I haven't been able
to find anything through Google searches. I have a container that also
has it's own attributes. I am calling
zope.app.container.constraints.contains from IFosterRecord, is that what
is causing the __setitem__ problem?
Hi Rob,
__setitem__ is likely also part of your IFosterRecord interface.
class IFosterRecord(IContainer) #?
and this is causing the conflict.
Regards,
Darryl
On Tue, 2006-09-19 at 15:35 -0700, Rob Campbell wrote:
I know I read about this error somewhere before, but I haven't been able
to
14 matches
Mail list logo
