On Jun 22, 2009, at 2:51 PM, Martijn Faassen wrote:
Jim Fulton wrote:
[snip[
I made it possible to override proxying by overriding the proxy
method. At this point, I think zope.app.publication provides a
pretty
reasonable base class for custom publication implementations,
although
Jim Fulton wrote:
They wouldn't. They don't use the URL traversal code. Non-URL
traversal code would move to zope.tales. zope.container would depend
on zope.tales rather than on zope.traversing.
For my own education, I would like to understand why it makes sense for
zope.container to
On Jun 23, 2009, at 2:36 PM, Shane Hathaway wrote:
Jim Fulton wrote:
They wouldn't. They don't use the URL traversal code. Non-URL
traversal code would move to zope.tales. zope.container would
depend on zope.tales rather than on zope.traversing.
For my own education, I would like to
Jim Fulton wrote:
On Jun 23, 2009, at 2:36 PM, Shane Hathaway wrote:
Jim Fulton wrote:
They wouldn't. They don't use the URL traversal code. Non-URL
traversal code would move to zope.tales. zope.container would depend
on zope.tales rather than on zope.traversing.
For my own
On Jun 23, 2009, at 3:02 PM, Shane Hathaway wrote:
Jim Fulton wrote:
On Jun 23, 2009, at 2:36 PM, Shane Hathaway wrote:
Jim Fulton wrote:
They wouldn't. They don't use the URL traversal code. Non-URL
traversal code would move to zope.tales. zope.container would
depend on zope.tales
On Sun, Jun 21, 2009 at 11:55:50AM -0400, Jim Fulton wrote:
- It aggressively proxies objects using
zope.security.checker.ProxyFactory. Some people don't want
to use proxies and those that do might want to use a different
proxy or checker implementation.
Grok's publication sub-class
On Jun 21, 2009, at 9:40 PM, Stephan Richter wrote:
On Sunday 21 June 2009, Jim Fulton wrote:
Thoughts?
+1. Sounds really good!
BTW, I would love to hear about a practical example for overriding
proxy()
other than turning off security altogether.
2 examples:
- Use a Python-based
HI
Big +1 from me on this.
I had to do a whole lot of hacks to get this stuff running on app engine and
basically
had to gut zope.proxy which was ugly and obviously unsupported.
After getting this running which was a big task I decided to go with
repoze.bfg which
just didn't have the security
On Jun 22, 2009, at 4:08 AM, Brian Sutherland wrote:
On Sun, Jun 21, 2009 at 11:55:50AM -0400, Jim Fulton wrote:
- It aggressively proxies objects using
zope.security.checker.ProxyFactory. Some people don't want
to use proxies and those that do might want to use a different
proxy or
On Jun 21, 2009, at 1:32 PM, Tres Seaver wrote:
...
Thoughts?
+1. I would also like to be able to break the current
zope.app.publication dependencies within Zope2:
- ZPublisher.BaseRequest uses zope.app.publication for the
EndRequestEvent class
- Products.Five.compuonent likewise uses
On Jun 22, 2009, at 7:11 AM, Tim Hoffman wrote:
Big +1 from me on this.
Cool.
I had to do a whole lot of hacks to get this stuff running on app
engine and basically
had to gut zope.proxy which was ugly
How so?
and obviously unsupported.
I don't think so. What makes you think it's
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim Fulton wrote:
On Jun 22, 2009, at 7:11 AM, Tim Hoffman wrote:
Big +1 from me on this.
Cool.
I had to do a whole lot of hacks to get this stuff running on app
engine and basically
had to gut zope.proxy which was ugly
How so?
and
On Jun 22, 2009, at 9:22 AM, Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim Fulton wrote:
On Jun 22, 2009, at 7:11 AM, Tim Hoffman wrote:
Big +1 from me on this.
Cool.
I had to do a whole lot of hacks to get this stuff running on app
engine and basically
had to
Hi Jim
Yeah I meant my ugly hacks getting rid of the 'c' in zope.proxy and
zope.security
aren't going to get supported by anyone, whereas having a supported way of
substituting proxies and security would be great. All the import
dependancies that existed when I went through the excercise meant
On Monday 22 June 2009, Jim Fulton wrote:
2 examples:
- Use a Python-based proxy that's good enough for supporting access
control in trusted code. (It wouldn't protect against devious
untrusted code, but most applications don't really need to run
untrusted code.)
- Use a better
On Mon, Jun 22, 2009 at 09:01:16AM -0400, Jim Fulton wrote:
- Create zope.publication from zope.app.publcatiobn
- use webtest rather than zope.app.testing.
What's webtest?
http://pythonpaste.org/webtest/
It's sort of like zope.app.testing.functional or zope.testbrowser but
for WSGI
Jim Fulton wrote:
[snip[
I made it possible to override proxying by overriding the proxy
method. At this point, I think zope.app.publication provides a pretty
reasonable base class for custom publication implementations, although
the module arrangement could be made a bit simpler.
I'm trying to make the Zope Toolkit (ZTK) publisher/publication
framework a little easier to deal with. I think zope.app.publication
mostly provides a generally useful publication implementation. It has
2 problems:
- Its getApplication method digs a particular object out of a ZODB
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim Fulton wrote:
I'm trying to make the Zope Toolkit (ZTK) publisher/publication
framework a little easier to deal with. I think zope.app.publication
mostly provides a generally useful publication implementation. It has
2 problems:
-
On Sunday 21 June 2009, Jim Fulton wrote:
Thoughts?
+1. Sounds really good!
BTW, I would love to hear about a practical example for overriding proxy()
other than turning off security altogether.
Regards,
Stephan
--
Entrepreneur and Software Geek
Google me. Zope Stephan Richter
20 matches
Mail list logo
