On Saturday 15 March 2003 5:40 pm, Chris McDonough wrote:
- The second is an unidentified (yet) bug in TemporaryStorage.
As a cause of the KeyError exception? Could be I have seen equivalent
exceptions with plain FileStorage in applications that do not use sessions,
so I suspect there
On Mon, 2003-03-17 at 04:31, [EMAIL PROTECTED] wrote:
I am trying to develop a program that generates a top-level folder
within zope and then has one of its functions called to give permission
to access the folder, as opposed to using the standard Zope permission
system.
I don't think you really
Hi Chris,
Chris McDonough wrote at 2003-3-15 12:40 -0500:
...
- The first is that turning off read conflicts allows for the potential
for the session data bucket and the session data index to become out
of sync. I admit that I knew this already, but haven't figured out
a way
On March 17, [EMAIL PROTECTED] wrote:
I am trying to develop a program that generates a top-level folder
within zope and then has one of its functions called to give permission
to access the folder, as opposed to using the standard Zope permission
system. As I understand it the only way to do
Hello,
I have tried call a function via XMLRPC with * and ** args
with no success!
The following error have appeared:
Unexpected Zope error value:
Traceback (most recent call last):
File
Toby Dickenson wrote:
Read conflicts occur if a change is committed in between the start of a
transaction, and the transaction needing to load the object. A workaround to
reduce the number of read conflicts is to touch the objects that are likely
to change early in the transaction.
Thanks
Hello,
Sorry, I made mistake on last patch...
I am sending the correct one
--- mapply.py 2003-03-17 20:11:23.0 -0300
+++ mapply.py.new 2003-03-17 20:11:16.0 -0300
@@ -13,6 +13,8 @@
Provide an apply-like facility that works with any mapping object
+import inspect
+
John Eikenberry wrote:
Toby Dickenson wrote:
Read conflicts occur if a change is committed in between the start of a
transaction, and the transaction needing to load the object. A workaround to
reduce the number of read conflicts is to touch the objects that are likely
to change
