February 2003 - Zope-Dev

Why is it _setObject(), and why is it undocumented
by maxm 05 Feb '03

05 Feb '03

I have a few tutorials / How_to's on zope.org. And sometimes I get some interresting mails because of that. Somebody asked me today why _setObject() has that name, as it is used in many products, and thus ought to be an interface method. And called something like "setObject()" or "manage_setObject()" And also he didn't understand why it wasn't documented anywhere. So why is that? does anybody know? regards Max M

6 10

Music, Film, Screenplays - It's all here!
by Jeff from TalentMatch.com 05 Feb '03

05 Feb '03

TalentMatch.com, featured in the news today has launched its much talked about entertainment site featuring independent bands, musicians, models, directors, actors and comedians from all over the world. You can listen to a Emmy-nominated singer/songwriter, bands of all genres from all over the world, a comedian who has appeared on "The Tonight Show" 12 times, European Models, see short films from Sundance directors! It's all here and it's all FREE! Smash or Trash, Short films, Chat, Mail, Music Videos, Post Music...it's all FREE for talent and fans worldwide! Check it out today! TalentMatch.com, click here: <http://www.talentmatch.com/> If this email has reached you in error, or you wish to unsubscribe from future emails, please unsubscribe at: OptOut(a)TalentMatch.com

1 0

Creating a variable in a DTML method that may be modified
by Asad Habib 04 Feb '03

04 Feb '03

Hello. Does anyone know how to create a variable in a DTML method which may be updated by a Python script? I am currently using the set method of the REQUEST object to create a variable. However, creating a variable in this fashion renders it permanent. Any help would be appreciated. Thanks. -Asad __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com

2 1

Testing a value returned from a Zope Python Script
by Asad Habib 04 Feb '03

04 Feb '03

Hello. I am trying to test a value returned from a Python script using the following syntax: <dtml-if expr="<dtml-call expr="checkRowLength(fileObject_index, rowLength)"> == 0"> </dtml-if> checkRowLength is the name of the script. Apparently Zope flags me with an error saying that this is an invalid attribute tag for a dtml-if. Is there any other way of achieving this? Any help would be appreciated. -Asad __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com

2 1

ExternalEditor losing its lock?
by Jean Jordaan 04 Feb '03

04 Feb '03

Hi all A couple of times now, I've noticed this: - I open a Python Script using ExternalEditor. A GET is issued, My editor starts up, and a LOCK gets set. - Now I view and execute the script (more GETs) while editing and saving in my editor (PUTs get issued). - That's fine. But then the lock goes away, and I successfully edit the script in the ZMI: a POST goes thru. But there hasn't been any UNLOCK yet. This shouldn't happen, right? (Zope 2.5.1 (source release, python 2.1, linux2), python 2.1.3, linux2) Excerpt from Z2.log: 192.168.1.5 - jean [03/Feb/2003:18:25:38 +0200] "GET /externalEdit_/test HTTP/1.1" 200 1088 "http://blommie:17081/manage_main" "Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20021212" 192.168.1.5 - jean [03/Feb/2003:18:25:40 +0200] "LOCK /test HTTP/1.1" 200 789 "" "Zope External Editor/0.6" 192.168.1.5 - jean [03/Feb/2003:18:25:56 +0200] "PUT /test HTTP/1.1" 204 251 "" "Zope External Editor/0.6" 192.168.1.5 - jean [03/Feb/2003:18:25:58 +0200] "GET /test/manage_workspace HTTP/1.1" 302 467 "http://blommie:17081/manage_main" "Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20021212" 192.168.1.5 - jean [04/Feb/2003:10:32:25 +0200] "PUT /test HTTP/1.1" 204 251 "" "Zope External Editor/0.6" 192.168.1.5 - jean [04/Feb/2003:10:46:11 +0200] "POST /test HTTP/1.1" 200 12877 "http://blommie:17081/test/ZPythonScriptHTML_editForm" "Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20021212" 192.168.1.5 - jean [04/Feb/2003:10:46:11 +0200] "GET /manage_page_style.css HTTP/1.1" 200 3014 "http://blommie:17081/test" "Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20021212" 192.168.1.5 - jean [04/Feb/2003:10:46:16 +0200] "PUT /test HTTP/1.1" 204 251 "" "Zope External Editor/0.6" 192.168.1.5 - jean [04/Feb/2003:10:46:18 +0200] "GET /test/manage_workspace HTTP/1.1" 302 467 "http://blommie:17081/test" "Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20021212" -- Jean Jordaan http://www.upfrontsystems.co.za

2 1

[Bug] Zope's transaction behaviour flawed
by Dieter Maurer 04 Feb '03

04 Feb '03

Zope's current transaction behaviour is essentially: ## request starts transaction.begin() try: object= REQUEST.traverse(...) mapply(object,...) transaction.commit() except: transaction.abort() handle_error() ## request ends This is flawed as error handling is done outside of a transaction. Potential changes during the error handling spill over uncontrolled into another request and are there either committed or aborted as part of this request. Andrew Athan (<mailto:aathan@memeplex.com>) has had lots of serious inconsistencies in Zope's session data. After extensive analysis, he found out that reading the session data during error handling led to these error conditions (reading session data causes writes to the administrative data). I suggest, we let Zope perform error handling in its own transaction after the original transaction had been aborted. When error handling succeeds, its transaction is committed, otherwise aborted. The new behaviour would look something like this: ## request starts transaction.begin() try: object= REQUEST.traverse(...) mapply(object,...) transaction.commit() except: transaction.abort() transaction.begin() transaction.note('%s (application error handling)' % '/'.join(object.getPhysicalPath) ) try: handle_error() transaction.commit() except: default_handle_error() # Zope's default error handling # it should not have side effects # and is executed inside the # error handling transaction transaction.abort() ## request ends Dieter

6 13

ZODB3 3.1.1b2
by barry＠zope.com 03 Feb '03

03 Feb '03

We've made another beta release of ZODB 3.1.1 available, including ZEO 2.0.2. This is primarily a bug fix release; see the NEWS.txt file excerpt below for details. Of particular note are the enabling of the BTrees-based index for FileStorage and the disabling of the rare "hosed" state in ZODB. This release corresponds to Zope 2.6.1b2 which was release on Friday 31-Jan-2003. (The releases differ only in some inconsequential Windows test modules.) For more information, including links to download, please see: http://www.zope.org/Products/ZODB3.1 See also the ZODB wiki page for all things ZODB: http://www.zope.org/Wikis/ZODB Enjoy, -Barry & Jeremy What's new in ZODB3 3.1.1 beta 2? ================================= Release date: 03-Feb-2003 The Transaction "hosed" feature is disabled in this release. If a transaction fails during the tpc_finish() it is not possible, in general, to know whether the storage is in a consistent state. For example, a ZEO server may commit the data and then fail before sending confirmation of the commit to the client. If multiple storages are involved in a transaction, the problem is exacerbated: One storage may commit the data while another fails to commit. In previous versions of ZODB, the database would set a global "hosed" flag that prevented any other transaction from committing until an administrator could check the status of the various failed storages and ensure that the database is in a consistent state. This approach favors data consistency over availability. The new approach is to log a panic but continue. In practice, availability seems to be more important than consistency. The failure mode is exceedingly rare in either case. The BTrees-based fsIndex for FileStorage is enabled. This version of the index is faster to load and store via pickle and uses less memory to store keys. We had intended to enable this feature in an earlier release, but failed to actually do it; thus, it's getting enabled as a bug fix now. Two rare bugs were fixed in BTrees conflict resolution. The most probable symptom of the bug would have been a segfault. The bugs were found via synthetic stress tests rather than bug reports. A value-based consistency checker for BTrees was added. See the module BTrees.check for the checker and other utilities for working with BTrees. A new script called repozo.py was added. This script, originally written by Anthony Baxter, provides an incremental backup scheme for FileStorage based storages. zeopack.py has been fixed to use a read-only connection. Various small autopack-related race conditions have been fixed in the Berkeley storage implementations. There have been some table changes to the Berkeley storages so any storage you created in 3.1.1b1 may not work. Part of these changes was to add a storage version number to the schema so these types of incompatible changes can be avoided in the future. Removed the chance of bogus warnings in the FileStorage iterator. ZEO --- The ZEO version number was bumped to 2.0.2 on account of the following minor feature additions. The performance of full cache verification has improved dramatically. XXX Get measurements from Jim -- somewhere in 2x-5x recall. The implementation was fixed to use the very-fast getSerial() method on the storage instead of the comparatively slow load(). The ZEO server has an optional timeout feature that will abort a connection that does not commit within a certain amount of time. The timeout works by closing the socket the client is using, causing both client and server to abort the transaction and continue. This is a drastic step, but can be useful to prevent a hung client or other bug from blocking a server indefinitely. If a client was disconnected during a transaction, the tpc_abort() call did not properly reset the internal state about the transaction. The bug caused the next transaction to fail in its tpc_finish(). Also, any ClientDisconnected exceptions raised during tpc_abort() are ignored. ZEO logging has been improved by adding more logging for important events, and changing the logging level for existing messages to a more appropriate level (usually lower).

1 0

RE: [Zope-dev] ESI Integration in Zope
by sean.upton＠uniontrib.com 03 Feb '03

03 Feb '03

Out of curiosity, Beyond coding XHTML-based ZPTs with tags in the ESI namespace, what else is needed in Zope to make this work? Does Zope need to set an HTTP header for downstream proxies to know that the content of the page is supposed to be processed for ESI? Sean -----Original Message----- From: Brian Lloyd [mailto:brian@zope.com] Sent: Thursday, January 30, 2003 1:12 PM To: zope-dev(a)zope.org Subject: RE: [Zope-dev] ESI Integration in Zope > What is the roadmap for ESI integration in zope ? > (http://www.zope.com/News/PressReleases/OpenSourceESI) > > In which version of zope : 2.6, 2.7 or 3.0 ? > > Thanks. We're shooting for Zope 2.7. Jim still needs to work out a lingering issue with it. Brian Lloyd brian(a)zope.com V.P. Engineering 540.361.1716 Zope Corporation http://www.zope.com _______________________________________________ Zope-Dev maillist - Zope-Dev(a)zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )

2 1

Running Python Scripts via the Management Interface
by Asad Habib 03 Feb '03

03 Feb '03

Hello. Does anyone know why the following script stalls when I run it in Zope's Management Interface using the 'Test' command? context.manage_addProperty(propertyId, propertyValue, propertyType) All it does is add a property to a folder. The script does function properly and doesn't stall when I access it from a DTML method. However, it stalls when I run it directly. Any help would be appreciated. Thanks. -Asad __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com

2 1

Re: [Zope] Header information on file upload
by Martin Gebert 02 Feb '03

02 Feb '03

Florent Guillaume wrote: >The File and Image objects use the Content-Type header on upload if it >is provided by the browser. Only if none is provided does it guess one. >See OFS.Image.File._get_content_type(). > > What brings me directly to the central question: Is this Content-Type header provided reliably by every browser? Or: How often must the fallback behaviour be used? Thanks for answers! Martin

2 1