Folder uses an OOBTree to store it's data, so it should be ok. But if you
want to use BTreeContainer and have it work as a Site, you just have the mix
the two together in a custom container class:
from zope.app.container.interfaces import IContainer
from zope.app.component.interfaces import
On Tuesday 08 July 2008, andrew wrote:
I've got a web application that uses pluggable authentication, but I
don't want the overhead of authentication for public resources like CSS,
javascript, images, etc. Is it possible to just disable authentication
for a given resource ? I tried just
Hi, ok change python2.4 to python2.5. but I get errors. I have installed
setuptools-0.6c8, but z3ext installs setuptools-0.6c7-py2.5.egg.
I have had other problems in others modules because they wore the
setuptools-0.6c7. It was resolved with the version 0.6c8
(sorry for my english)
$python2.5
On Wed, 2008-07-09 at 08:39 -0500, Randy Crafton wrote:
Folder uses an OOBTree to store it's data, so it should be ok.
Thanks. I believe that solves my issue. :-)
But if you want to use BTreeContainer and have it work as a Site, you
just have the mix the two together in a custom container
Hi All,
On Tue, 2008-07-08 at 22:52 -0700, Shailesh Kumar wrote:
Did you try the resourceDirecotry ZCML directive?
browser:resourceDirectory
name=js
directory=resource/js
layer=.interfaces.IBatonSkin
/
that way they don't need the authentication overhead.
Thanks for the
Hi Andrew
Betreff: Re: [Zope3-Users] Disabling authentication for resources
[...]
I guess bypass the authentication process is not supported for
zope.Public protected objects.
Zope does authenticate the user. And later it checks security
for the object based on that user (authorization).
Hi,
I have couple of following settings in my etc\securitypolicy.zcml
role id=zope.Anonymous title=Everybody
description=All users have this role implicitly /
!-- Replace the following directive if you don't want public access --
grant permission=zope.View
On Thu, 2008-07-10 at 02:44 +0200, Roger Ineichen wrote:
I guess bypass the authentication process is not supported for
zope.Public protected objects.
Zope does authenticate the user. And later it checks security
for the object based on that user (authorization).
zope.Public is correct
