I just had a thread about SiteAccess that resulted with Dieter suggesting I
rewrite SiteAccess as an External Method to get around security limitations.
>>The security context is set after URL traversal.
>>At least, it is not easy to set it before.
This prevents the manipulation of session variables. In my case, I am using
embedded session variables and writing it to a database.
So, based on my current requirement, I request to put more security options
in SiteAccess, to allow AccessRules to be used during URL traversal.
Allow the Security tab context to apply to AccessRules, so they can be
executed by "Anonymous User".
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf
> Of emf
> Sent: Saturday, November 24, 2001 3:13 AM
> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: [Zope-dev] SiteAccess improvements
> There's a very nearly "orphaned proposal":
> iMeme has already done some work towards these goals with
> I am taking over this effort, and I have some near-term "goals outlined":
> I intend to deliver the VHM improvements before the AccessRule
> Please give feedback on this proposal, and let me know what I need to do
> to move this into the project phase.
> ethan mindlace fremen | iMeme - The most full featured Zope Host
> http://mindlace.net | Root, ZEO, MySQL, Mailman, Unlimited Domains
> iMeme Partner | http://iMeme.net
> "It is our desire to remain what we are that limits us. -- Project 2501"
> Zope-Dev maillist - [EMAIL PROTECTED]
> ** No cross posts or HTML encoding! **
> (Related lists -
> http://lists.zope.org/mailman/listinfo/zope )
Zope-Dev maillist - [EMAIL PROTECTED]
** No cross posts or HTML encoding! **
(Related lists -