July 1999 - Zope-Dev

New ZClass based on Users
by Jason Spisak 07 Jul '99

07 Jul '99

Zopists, Has anyone tried to create a new ZClass based on User Folder, and then put a class based on Users in it? I would like to give the users of my site some properties other than Roles, and Domain., etc... I know that this is what the ZPTK is all about. Just wondering if anyone's had any luck so that I don't have to start from sratch. All my best, Jason Spisak webmaster(a)mtear.com

1 0

Re: ZClass "delete" and Catalog disk tuning
by Jason Spisak 06 Jul '99

06 Jul '99

An Update to the latest CVS and a recompile fixed the KeyError "delete". I don't even know what it might have been. The glory of CVS :) >searching an index is much faster, That is all we will be doing. >incrimental indexing is much more efficient because it typically only wakes up a portion of the index. I will be setting up indexes for each findable property separately, and in regards to MetaData, very few actual items will get returned. Mostly the search results will point you to the actual items to keep it lightweight. After all, it's only a click away :) Oh, in regards to reads and writes to disk, mostly would you say Zope does non-sequencial reads and writes? (ie from a lot of various places, where disk I/O would be a primary bottleneck) Jason Spisak webmaster(a)mtear.com

1 0

RE: [Zope-dev] Re: ZODB3 Database question/server tuning
by Michel Pelletier 06 Jul '99

06 Jul '99

> -----Original Message----- > From: Jason Spisak [mailto:webmaster@mtear.com] > Sent: Tuesday, July 06, 1999 12:44 PM > To: zope-dev(a)zope.org > Subject: [Zope-dev] Re: ZODB3 Database question/server tuning > > > Zopists, > > I'm not sure who to ask this to so I'll throw it out and see > if anybody > knows. > > As far as disk/server performance and the Data.bbb file, it's > not like a > traditional RDB as far as disk performance and speed goes right? > Assuming I'm not connecting to any backend DB's, is it just one large > file always in the same place? With the advent of ZODB3 how does Zope > handle many people asking for different protions of the database? > > (I don't think my question is clear yet, I'll keep trying:) > > Does Zope store the entire Data.bbb file into memory if it can? Zope stores recently accessed objects in memory. It deactivates them according to how you tune the cache in the Control Panel. > In > which case lots od RAM matters and hard disk speed doesn't accept for > start-up. Are there lots of random reads/writes to disk if > say 150 are > all creating records at the same time and searching, etc...? > Or are the > writes to disk sequencial because it's only one file (Data.bbb)? All writes to the Data.bbb file are appended onto the end of the file. Note that even though Zope 'writes' something 'out to file' the OS may in fact be buffering large amounts of the reads and writes in memory. Linux, for example, will use as much available RAM as it can for file buffers and caches. Other UNIXish OSes probably behave similarly. The more RAM you have, the less actual disk reading and writing goes on. Finding and searching a catalog are two different access paterns. Finding walks down the Zope tree examining objects for certain attributes. This is similar to the UNIX 'find' utility. It is slow and rather expensive. searching an index is much faster, but possible more memory comsuming. searching involves pre-indexing a bunch of data ito a very fast binary tree. Only the portions of the index that are being searched are activated in memory, and unused portions are deactivated. This is why mass-indexing makes the Zope process grow so large. Because almost the entire index is activated to index everything in your site, the whole thing is in memory. incrimental indexing is much more efficient because it typically only wakes up a portion of the index. We are working on more and more optimizations for indexing, including pre-sorting the indexed information in tmp files, so that various portions of the index can be woken up and put to sleep in an orderly fasion, instead of randomly as it is now (requiring the consumption of large amounts of memory). -Michel > > I'm sure this is quite confusing. Sorry. I'm trying to see what the > best server tuning would be for Zope. Thanks for your patience. > > All my best, > > Jason Spisak > webmaster(a)mtear.com > > _______________________________________________ > Zope-Dev maillist - Zope-Dev(a)zope.org > http://www.zope.org/mailman/listinfo/zope-dev > > (For non-developer, user-level issues, use the companion list, > zope(a)zope.org, http://www.zope.org/mailman/listinfo/zope ) >

1 0

Re: ZODB3 Database question/server tuning
by Jason Spisak 06 Jul '99

06 Jul '99

Zopists, I'm not sure who to ask this to so I'll throw it out and see if anybody knows. As far as disk/server performance and the Data.bbb file, it's not like a traditional RDB as far as disk performance and speed goes right? Assuming I'm not connecting to any backend DB's, is it just one large file always in the same place? With the advent of ZODB3 how does Zope handle many people asking for different protions of the database? (I don't think my question is clear yet, I'll keep trying:) Does Zope store the entire Data.bbb file into memory if it can? In which case lots od RAM matters and hard disk speed doesn't accept for start-up. Are there lots of random reads/writes to disk if say 150 are all creating records at the same time and searching, etc...? Or are the writes to disk sequencial because it's only one file (Data.bbb)? I'm sure this is quite confusing. Sorry. I'm trying to see what the best server tuning would be for Zope. Thanks for your patience. All my best, Jason Spisak webmaster(a)mtear.com

1 0

RE: [Zope-dev] Catalog aware ZClass
by Michel Pelletier 06 Jul '99

06 Jul '99

> -----Original Message----- > From: Jason Spisak [mailto:webmaster@mtear.com] > Sent: Monday, July 05, 1999 6:31 PM > To: zope-dev(a)zope.org > Subject: [Zope-dev] Catalog aware ZClass > > > Michel: > > Thanks for the Findable base class ideas. I attempted to create a > Findable class and made a small mistake. I named the method > to perform > deletion "delete" Of course now anyhting to do with that object > produces a KeyError. I can't delete it, or look inside it. Just a > heads up on the taboo name "delete" in ZClasses. Is there any other > taboo names I should be aware of? > Hmm. I'm a little lost here, you created a Findable ZClass with a delete method, and that broke? I'm not sure how, I don't think 'delete' is a special word of any kind. Just for safties sake however, you might want to come up with more obfusicated nameds. > Also you mentioned add, delete and findable methods for this > base class. > Doesn't adding something to the Catalog automatically render it > findable? > Yep, 'Findable' is just a handy name for a base class that defines the attributes you want to find. It is possible for you to add indexes that don't correlate with the Findable class, and conversely it is possible for Findable to define attributes that the catalog doesn't look for. The two are unconnected, it's just handy to keep all of your 'Findables' in one base class, that way lots of different kinds of ZClasses can subclass Findable and thus work seamlessly with your existing catalogs. -Michel PS Catalog beta is around the corner, expect it with the next Zope alpha. > All my best, > > -- > Jason Spisak > webmaster(a)mtear.com > > _______________________________________________ > Zope-Dev maillist - Zope-Dev(a)zope.org > http://www.zope.org/mailman/listinfo/zope-dev > > (For non-developer, user-level issues, use the companion list, > zope(a)zope.org, http://www.zope.org/mailman/listinfo/zope ) >

1 0

RE: [Zope-dev] New ZPublisher Types
by Martijn Pieters 06 Jul '99

06 Jul '99

At 20:08 05/07/99 , Pam Crosby wrote: >Cathi, >Your documentation has been added to the Trinkets Tutorial online at >http://www.zope.org/Documentation/Reference/Trinkets/index_html Very nice! These changes are only available in the latest CVS release, however. How will a new developer be able to detect this from the documentation? Some errors: -- RECORD <INPUT TYPE="text" NAME="person.name:record" SIZE="30"> The input tag for the name field is named person.name:record:ignore_empty. The :record part of the name indicates to Zope that the field should be converted to a record before passing it to the published method. A record variable will be created called person and it will have an attribute called name. - Either: The first line should read: .. is named person.name:record. The .. - Or: the NAME field of the INPUT tag should read: person.name:record:ignore_empty -- RECORDS The records method is implemented: <P><H2>Member #1<H2></P><br> <P>lease enter your name:<BR> <INPUT TYPE="text" NAME="member.name:records:ignore_empty" SIZE="30"><BR> your email:<BR> <INPUT TYPE="text" NAME="member.email:records:ignore_empty" SIZE="30"><BR> your age:<BR> <INPUT TYPE="hidden" NAME="myname.age:int:records:default" Value="0"<BR> <INPUT TYPE="text" NAME="member.age:int:records:ignore_empty"></P><BR> <P><H2>Member #2</H2></P><BR> <P>Please enter your name:<BR> <INPUT TYPE="text" NAME="member.name:records:ignore_empty" SIZE="30"><BR> your email:<BR> <INPUT TYPE="text" NAME="member.email:records:ignore_empty" SIZE="30"><BR> your age:<BR> <INPUT TYPE="text" NAME="member.age:int:records:ignore_empty<a href="records"">></P> In this sample the form asks for a name and age for two different members of a club. The part appears in each input tag. This type will create a list called members that will hold records (in this case it will hold two records). Each record can have the attributes name and age. - The hidden field should read: .. NAME="member.age:int:records:default" .. - A newline before the line 'Member #2' would increase readability. -- -- Martijn Pieters, Web Developer | Antraciet http://www.antraciet.nl | Tel: +31-35-7502100 Fax: +31-35-7502111 | mailto:mj@antraciet.nl http://www.antraciet.nl/~mj | PGP: http://wwwkeys.nl.pgp.net:11371/pks/lookup?op=get&search=0xA8A32149 ------------------------------------------

1 0

a SERIOUS APPLICATION ERROR !!!
by HCSCCS＠prudential.com.my 06 Jul '99

06 Jul '99

Recently, I got the External Method running fine. But after coming back from vacation for 5 days, I received the above error when running testing the External Method. The error was pointing to an import error. All the External Methods are stored in the Extensions directory. That particular method actually import a python file that resides in the same dir. I also added an entry in PYTHONPATH env variable so that it points to the Extensions directory. So what's wrong ??? Please cc a copy to this address hcsccs(a)prudential.com.my. Thanks, PauL ChunG

1 0

RE: [Zope-dev] DocumentTemplate packaging suggestion
by Alexander Staubo 06 Jul '99

06 Jul '99

>-----Original Message----- >From: zope-dev-admin(a)zope.org [mailto:zope-dev-admin@zope.org]On Behalf >Of Phillip J. Eby >Sent: 3. juli 1999 14:34 >To: zope-dev(a)zope.org >Subject: [Zope-dev] DocumentTemplate packaging suggestion > > >Now that all of Zope is Open Source, might it make sense to >move the tree >tag and sql* tags to the DocumentTemplate package, since they >don't really >require the rest of Zope, and make useful additions to >DocumentTemplate in >its own right? It seems to me that adding them as dynamically >loaded tags >would enhance the value of the DocumentTemplate package. The >sendmail tag >of course wouldn't make sense because it requires a MailHost >object, but >the other tags do not require any ZInfrastructure besides >DocumentTemplate. > Right now, I have to surgically excise the .py files from the Zope >distribution and find some reasonable place in my ZPublished >code to import >them, and then repeat the process whenever either Zope or >DocumentTemplates >are updated. > >Although it could be argued that the sql* tags shouldn't be in >the "core" >package, if they're dynamically loaded it doesn't affect much. > In fact, >they're quite useful there, as I've occasionally found the need to call >regular DTML from SQL methods in order to break up big queries >into smaller >chunks or to share common code between multiple queries. > >While I'm on the subject of DocumentTemplates, a seperate and entirely >unrelated suggestion that would be a lot more difficult than >the one above, >but might perhaps be more relevant for Zope's core audience of content >developers... A Zope newbie I was helping the other day found >the message >"KeyError" to be hopelessly confusing, when what they'd done >was misspelled >a variable name. Perhaps certain exceptions should be >re-formatted by the >DTMLDoc/DTMLMethod classes so that Zope displays more >meaningful messages >like "Unrecognized name: foo", instead of the weird public-traceback + >hidden error data combo. No implications of imbecility intended, but you can do this by customizing standard_error_message. The DTML of the default message method actually gives a nice example of how it can be tweaked: <P>Troubleshooting Suggestions</P> <UL>  <LI>This resource may be trying to reference a nonexistent object or variable <STRONG></STRONG>.</LI>  <LI>The URL may be incorrect.</LI> <LI>The parameters passed to this resource may be incorrect.</LI> <LI>A resource that this resource relies on may be encountering an error.</LI> </UL> What annoys me more about error messages is that the whole error reporting thing is quite lacking: - Sometimes it just goes "(See above)", and sometimes the "Error Value" just says "Sorry, an error occurred". It would have been a lot neater if it could point out the exact part of the DTML that caused problems, which I realize is difficult due to the compiled nature of DTML, but that's not my concern. ;-) - Furthermore the traceback "lies" when dealing with External Methods: The correct Python error is never revealed, perhaps for security reasons. - And I wish, very dearly, that I could insert the traceback _as part of the HTML_. Right now Zope just adds the traceback to the end of the HTML, out of sight. For an excellent example of how dynamic error reporting should be done, check out MySQL. Or was that mSQL? Damn! Anyway, it -- whichever it is -- gives a very lucid, even aesthetically pleasing, error report, worthy of imitation. -- Alexander Staubo http://www.mop.no/~alex/ "What the hell, he thought, you're only young once, and threw himself out of the window. That would at least keep the element of surprise on his side." --Douglas Adams, _The Hitchhiker's Guide to the Galaxy_

1 0

Catalog aware ZClass
by Jason Spisak 05 Jul '99

05 Jul '99

Forgot the traceback: <!-- Traceback (innermost last): File /home/mike_weltz/Zope/lib/python/ZPublisher/Publish.py, line 256, in publish_module File /home/mike_weltz/Zope/lib/python/ZPublisher/Publish.py, line 161, in publish File /home/mike_weltz/Zope/lib/python/ZPublisher/mapply.py, line 154, in mapply (Object: manage_delObjects) File /home/mike_weltz/Zope/lib/python/ZPublisher/Publish.py, line 98, in call_object (Object: manage_delObjects) File /home/mike_weltz/Zope/lib/python/OFS/ObjectManager.py, line 382, in manage_delObjects (Object: Products) File /home/mike_weltz/Zope/lib/python/OFS/ObjectManager.py, line 254, in _delObject (Object: Products) File /home/mike_weltz/Zope/lib/python/OFS/ObjectManager.py, line 249, in manage_beforeDelete (Object: Findable) File /home/mike_weltz/Zope/lib/python/ZClasses/ZClass.py, line 371, in manage_beforeDelete (Object: Findable) File /home/mike_weltz/Zope/lib/python/OFS/ObjectManager.py, line 246, in manage_beforeDelete (Object: methods) File /home/mike_weltz/Zope/lib/python/OFS/ObjectManager.py, line 280, in objectValues (Object: methods) File /home/mike_weltz/Zope/lib/python/ZClasses/Method.py, line 201, in _getOb (Object: methods) File /home/mike_weltz/Zope/lib/python/ZClasses/ZClass.py, line 450, in getClassAttr (Object: Findable) KeyError: delete -- Jason Spisak webmaster(a)mtear.com

1 0

Catalog aware ZClass
by Jason Spisak 05 Jul '99

05 Jul '99

Michel: Thanks for the Findable base class ideas. I attempted to create a Findable class and made a small mistake. I named the method to perform deletion "delete" Of course now anyhting to do with that object produces a KeyError. I can't delete it, or look inside it. Just a heads up on the taboo name "delete" in ZClasses. Is there any other taboo names I should be aware of? Also you mentioned add, delete and findable methods for this base class. Doesn't adding something to the Catalog automatically render it findable? All my best, -- Jason Spisak webmaster(a)mtear.com

1 0