Dieter Maurer wrote:
Your test looks quite innocent.
I tried to reproduce it (about 5.000 ab requests against
something similar to your mon-clear) and could not see
any memory leak. Especially, no HTTPRequest or ImplicitAcquirerWrapper
were leaked.
However, you may have an AccessRule (or some
Johan Carlsson wrote:
So where should I send the patch, I'm not currently
active as a Zope contributor.
Whack it in the collector...
Chris
--
Simplistix - Content Management, Zope Python Consulting
- http://www.simplistix.co.uk
___
Clemens Robbenhaar wrote:
Ok, if this is the proper dance to catch such exceptions with Zope
without risking ZODB corruption I will go with it. So far I have not
been sure, that ConflictError is the only type needing special
treatement in these cases.
Well, the PROPER dance would be to only catch
Dieter Maurer wrote:
try: DB__=dbc()
except:
exc_type, exc_value, trc = sys.exc_info()
raise DatabaseError('%s is not connected to a database' % self.id,
exc_type,
exc_value), trc
I didn't know you could re-raise a traceback like
Shane Hathaway wrote:
That sounds mighty handy. What needs to happen for that to happen?
A voluntary volunteer needs to volunteer voluntarily.
I think I was offering to be such a person. So, what would such a person need to do?
Chris
--
Simplistix - Content Management, Zope Python Consulting
On Thu, Mar 25, 2004 at 10:23:27AM +, Chris Withers wrote:
Dieter Maurer wrote:
try: DB__=dbc()
except:
exc_type, exc_value, trc = sys.exc_info()
raise DatabaseError('%s is not connected to a database' % self.id,
exc_type,
Shane Hathaway wrote:
There certainly ought to be a way to create an unrestricted
PageTemplateFile, though it should be an explicit step.
That is a good suggestion. I'd like that option. It would also be a
potential performance benefit.
On the other hand, in situations where the PageTemplate
Martijn Faassen wrote:
Shane Hathaway wrote:
There certainly ought to be a way to create an unrestricted
PageTemplateFile, though it should be an explicit step.
That is a good suggestion. I'd like that option. It would also be a
potential performance benefit.
On the other hand, in
Jamie Heilman wrote:
Martijn Faassen wrote:
On the other hand, in situations where the PageTemplate designers are
*not* security conscious (they're designers, not primarily programmers)
the option of explicit checks is useful.
PageTemplateFile is a class used by Product authors, just like
Chris Withers writes:
Clemens Robbenhaar wrote:
Ok, if this is the proper dance to catch such exceptions with Zope
without risking ZODB corruption I will go with it. So far I have not
been sure, that ConflictError is the only type needing special
treatement in these cases.
Jamie Heilman wrote:
Martijn Faassen wrote:
Shane Hathaway wrote:
There certainly ought to be a way to create an unrestricted
PageTemplateFile, though it should be an explicit step.
That is a good suggestion. I'd like that option. It would also be a
potential performance benefit.
On the other
Dario Lopez-Ksten wrote:
Jamie Heilman wrote:
Martijn Faassen wrote:
On the other hand, in situations where the PageTemplate designers are
*not* security conscious (they're designers, not primarily
programmers) the option of explicit checks is useful.
PageTemplateFile is a class used by
Martijn Faassen wrote:
I'm advocating an explicit option to disable security checks here. I'm
just also advocating that the current behavior can be sensible in
certain circumstances. This is the only backwards compatible way anyway.
+1
Anyway, I disagree on the general philosophical point that
13 matches
Mail list logo
