- Zope-Dev - Zope lists

ANN: Zope Page Templates 1.0.0 beta 1
by Evan Simpson 27 Mar '01

27 Mar '01

The first beta release of ZPT is ready! Come read about them at http://dev.zope.org/Wikis/DevSite/Projects/ZPT, and download from http://www.zope.org/Members/4am/ZPT. These should be especially interesting for teams of Zope developers in which the programming and page/site design tasks are handled by separate people. Cheers, Evan @ digicool

1 0

Re: [Zope-dev] FTP interface being worked on?
by Karl Anderson 27 Mar '01

27 Mar '01

"Chris McDonough" <chrism(a)digicool.com> writes: > > > Are you thinking that we would build client-side tools to recognize an > XML > > > representation of a subpart of a site? > > > > Client-side tools, no. I'm thinking that exporting to XML would allow > > existing tools to recognize and manipulate a subpart of a site. > > Which ones? Parsers, transformers, etc.. I don't know of any end-user tools (are there any?), I'm talking about building blocks. > > Is there a particular set of tools or editing paradigms that we have > > in mind when we say that a non-XML representation is suited for client > > side tools? > > Yes.. anything that works well with diff and CVS and is recognizable by a > human. PythonScripts should be serialized to something that looks like a > regular Python script. Images should look like images, etc. The directory > tree generated should look as much as possible like a normal filesystem. Sure, I would use that, too, probably more than an XML representation, I'm referring to the ability to represent in other formats because of their usefulness and scalability. For example, if I were doing lots of random edits on a subtree of DTML files and Python scripts, I'd want them to look like a filesystem tree full of text files and I'd use emacs, grep, find, etc. on them. If I wanted to be able to use an automated tool to, say, update the spam and eggs fields of everyting in a subtree every friday, an XML parser and/or DOM tree and/or transform working on a single XML representation of the subtree checked out to the local filesystem seems like the easiest entry point. I'm probably straying from the proposal here. -- Karl Anderson karl(a)digicool.com

1 0

Zope/OpenBSD: Too many open files
by Ricardo Bermell 27 Mar '01

27 Mar '01

Zope (started from a shell) in OpenBSD gets locked too easyly because of the low default limit for open file descriptors (64). When Zope gets locked shows repeatedly this message "PROBLEM(100) ZServer warning: server accept() threw an exception", locking effectively also the console. Conditions in wich i have tested the problem: - OpenBSD 2.7 - Zope 2.3.0 - 'bash' shell How to reproduce the problem: 1. Anotate your current limit for open files (after this test you will want to restore this value): type "ulimit -a | grep 'open files'" My systems gives "open files 64" 2. If you want to crash zope sooner, set a lower limit (for example, 32) with "ulimit -n 32". 3. Start Zope from your shell (mine is 'bash') with zope 'start' script. Before, in the call to z2.py (in 'start') include option -D for 'debugging' (if not, all will be the same, exept that you won't see the "Problem(100)" message 4. Type "fstat | grep run-zope | grep stream | wc -l", (where 'run-zope' is the user account you use to run zope) or "fstat | grep 11789 | grep stream | wc -l" (where '11789' is the pid of zope process) That gives you the number of open streams for zope, which initially is 1. Each open stream consumes one file descriptor. 5. From a browser of another computer, open any (one) page of your zope site (http://your.zope.server:8080, where 8080 is the port you've open for zope). That will open 2 tcp streams in your server. Test, as before: "fstat | grep run-zope | grep stream | wc -l" This gives me 3 streams in total (1 initial + 2 for browser) 6. Close your browser and see how the open streams persists Type again: "fstat | grep run-zope | grep stream | wc -l" You will see 3 yet. 7. Repeat this operation many times (open browser, get http page, close browser), observing how the number of open streams increases in steps of 2. After m repetitions your browser does not get response from Zope: your Zope service and your console stops attending requests. 8. Stop your Zope from another console. (This liberates also the locked console) 9. Test distinct values for 'ulimit -n'. You will observe that, for a given value of 'ulimit -n' the number of repetitions (m) needed to hang your zope will be always the same. (You must run 'ulimit -n' _before_ run zope for it to get effect, not _while_ running zope) Questions which i'm not able to answer: - How many time an open tcp stream lives after you open a page from your browser? - How many time an open tcp stream lives after you close the browser (wich originated the stream)? the answer to those two questions will help to know: - How can i predict an adequate number for 'ulimit -n' (max. number of file/stream descriptors) in function of the utilization of my server? Unknowing wich is the perfect election, i've selected a limit of 1024 - Is it too many 1024? Too many resources utilization? But, the main question, IMHO, is that: - It is Zope robustness what fails. It should deny access gracefully when resources are exhausted. (Or at least, it should give comprehensive error information). Is it so? Or is it a wrong observation? I am now using zope only for developing static pages, not for a public dynamic service, and the 'ulimit' patch suffices, but i am afraid for when i'll want to put it in a public service with a heavy load. -- Ricardo P.S. I have tested also Zope 2.2.4 and 2.3.1b1 in OpenBSD. I didn't perform the 'ulimit' test in these versions but i do have experienced the "PROBLEM(100)" error (or similar). I have tested Zope 2.3.1b1 and 2.3.0 thru Apache and standalone. When thru Apache: with pcgi and with fastcgi. When with fastgi: with port and with socket.

1 0

Re: [Zope-dev] FTP interface being worked on?
by Karl Anderson 27 Mar '01

27 Mar '01

Chris McDonough <chrism(a)digicool.com> writes: > I think the only good reasons we have right now for having > filesystem-compatible serialization are to make Zope content editable via > common tools in a way that makes sense to people not used to (or comfortable > with) the object database, and to give people a plausible way to put a Zope > site under source control. > > Are you thinking that we would build client-side tools to recognize an XML > representation of a subpart of a site? Client-side tools, no. I'm thinking that exporting to XML would allow existing tools to recognize and manipulate a subpart of a site. I'm basically agreeing with you - "common tools" for manipulating text sounds like parsers to me. I'm not sure why XML is considered less readable than an unknown format for Zope object serialization; I guess I haven't seen what's being considered. But it seems to me that for humans, XML might lose by a little, but for any type of mediated or batch processing, XML wins by a lot. Parsers are standard enough that their APIs are easy to learn if you've played with them before. Random human-editable text formats sounds like StructuredText; when I think of StructuredText I think "simple DOM serialization". Is there a particular set of tools or editing paradigms that we have in mind when we say that a non-XML representation is suited for client side tools? This is the way that Manila seems to be doing it: http://www.thetwowayweb.com/theXmlFiles -- Karl Anderson karl(a)digicool.com

3 2

filter metatypes in objectmanager
by Magnus Heino 27 Mar '01

27 Mar '01

How can I control what meta_type's that can be added to an ObjectManager? If you create a ZClass that inherits from ObjectManager, you can specify this, but how is it done from a python product? /Magnus

2 1

Re: [Zope-dev] Images and Products
by Dieter Maurer 27 Mar '01

27 Mar '01

Andre Schubert writes: > I have a little Problem on using Images in my Product. > If i'am logged in as Manager i can View the Image, but if logged in as > Anonymous i can't view the Image. > The View permission is assigned to Anonymous Role and the Image Foo is > assing to the View Permission, but i can't view the Image as Anonymous. > > Source: > __ac_permissions=( > .... > ('View', ('index_html','Foo'), ('Manager',)), As Chris already pointed out: ^^^^^ does not work. > Foo = ImageFile('icons/foo.gif',globals()) > > Link: > http://www.somewhere.de/myProduct/Foo Access permissions are controlled by the permission of "ImageFile.index_html" which requires view permission. I expect, you have somehow broken the acquisition chain. Does your product inherits "Acquisition.{Ex|Im}plicit" or at least "ExtensionClass.Base"? If not, Zope's permission machinery will not work. Dieter

2 2

Compiling new Splitter.c on Windows
by Big John Holmes 27 Mar '01

27 Mar '01

Howdy all. It's been a while since I've posted because the company I used to work for is sliding into the sludge. So I'm working on my own now! Unfortunately that means I have to use Windows with Zope. Since I have no experience in this area I'll cut to the chase. I have aSplitter.c file written that works under linux, and I'd like to use it under Windows. How do I do it. I tried compiling the source distribution off Zope.org, but wo_pcgi.py starts and dies. What's the secret? All my best, Jason Spisak __________________________________________________ Do You Yahoo!? Get email at your own domain with Yahoo! Mail. http://personal.mail.yahoo.com/

6 9

Zope 2.3.1b3 problem
by Andy Dawkins 27 Mar '01

27 Mar '01

People I have found this small problem but I don't know where it is coming from or why. If you create a Python Script in a folder: ------- print container.id return printed ------- If fails with this error: Error Type: TypeError Error Value: call of non-function (type list) Traceback (innermost last): File /usr/zope/zope-2_3_1b3/lib/python/ZPublisher/Publish.py, line 223, in publish_module File /usr/zope/zope-2_3_1b3/lib/python/ZPublisher/Publish.py, line 187, in publish File /usr/zope/zope-2_3_1b3/lib/python/Zope/__init__.py, line 221, in zpublisher_exception_hook (Object: Traversable) File /usr/zope/zope-2_3_1b3/lib/python/ZPublisher/Publish.py, line 171, in publish File /usr/zope/zope-2_3_1b3/lib/python/ZPublisher/mapply.py, line 160, in mapply (Object: hmmmm) File /usr/zope/zope-2_3_1b3/lib/python/ZPublisher/Publish.py, line 112, in call_object (Object: hmmmm) File /usr/zope/zope-2_3_1b3/lib/python/Shared/DC/Scripts/Bindings.py, line 324, in __call__ (Object: hmmmm) File /usr/zope/zope-2_3_1b3/lib/python/Shared/DC/Scripts/Bindings.py, line 353, in _bindAndExec (Object: hmmmm) File /usr/zope/zope-2_3_1b3/lib/python/Products/PythonScripts/PythonScript.py, line 336, in _exec (Object: hmmmm) (Info: ({'script': <PythonScript instance at 83c9878>, 'context': <Folder instance at 874b608>, 'container': <Folder instance at 874b608>, 'traverse_subpath': []}, (), {}, None)) File Script (Python), line 2, in hmmmm (Object: <lambda>) TypeError: (see above) I have managed to reproduce this on Zope 2.3.1b2 and Zope 2.3.1b3 but it works fine on Zope 2.3.1b1 Any Ideas/Assistance? -Andy

3 5

More Core Session Tracking Woes :-(
by Chris Withers 26 Mar '01

26 Mar '01

Hi, The setup: -Zope 2.2.4 -Core Session Tracking 0.7 -Cookie session ID manager (path=/,lifetime=0) -Internal Session Data Manager (timeout set to 60 minutes) This seems to randomly (but sometimes very frequently) loose session data items :-( I've sprayed lots of log statements around (including in SessionData.invalidate, to ensure I wasn't inadvertently calling it) and so far it appears that the session id cookie is being returned by the browser (so path, lifetime, etc are probably okay) but self.session.getSessionData().get('Type','') is often returning an empty string, even when I know it has been set. This is an intermittent problem though, so it's probably going to be a bitch to track down :-( There's doesn't seem to be any correlation with the 'Can't Load State for x' problem I reported earlier, but I guess it could be the same thing. Anyway, please help, I'm loosing (hair|sleep|etc) over this :-( cheers, Chris

3 9

175 Million Email Addresses for $99 (4523)
by esys011＠excite.com 26 Mar '01

26 Mar '01

A half-page ad in the Sunday New York Times can cost more than $50,000 and only reaches 4 million people. | ~ | ~ | ~ | ~ | ~ | ~ | ~ | ~ | ~ | ~ | ~ | 175 MILLION EMAIL ADDRESSES FOR ONLY $99 | ~ | ~ | ~ | ~ | ~ | ~ | ~ | ~ | ~ | ~ | ~ | This "Special Offer" is in effect for a Limited Time only. This CD contains 136 Million email addresses and a list of 39 Million REMOVES, people who are known to request removal from emailers' lists. Knowing who NOT to send email to is as important as knowing WHO to send email to!!!! SO... provided you comply with the law, you can ADVERTISE your business, product, services or ideas to MILLIONS by sending email, and avoid 39 Million REMOVES!!! The whole list sells for only $99 and the addresses are yours to keep to use over and over!! These are FRESH addresses that include nearly every person on the Internet today, with NO DUPLICATIONS -- GUARANTEED!!!! Other people charge $250 for only 15 million names or even 10 million names. That means you would pay $2916 for 175 Million names. YOU ONLY PAY $99 !!!! REMEMBER: This "Special Offer" is in effect for a Limited Time only, so ACT NOW!!! ************************************************************************ TO ORDER BY PHONE USING A CREDIT CARD CALL OUR 24-HOUR ORDER DESK: ( 4 0 6 ) 6 5 7 - 1 8 1 8 ************************************************************************ Shipping costs (within the US, 3-5 business days) - $8.00 International shipping costs (typically 5-10 business days) - $35.00 C A L L N O W !!!!!!!!!!! ( 4 0 6 ) 6 5 7 - 1 8 1 8 ************************************************************************ THIS MESSAGE INCLUDES A REMOVE MECHANISM: Further transmissions by the sender may be stopped at no cost by replying to this message with the word "REMOVE" in the subject line. The remove process is AUTOMATED and all remove requests will be honored. The operators can only take orders and cannot assist in the remove process. Please understand that any effort to disrupt, close or block this REMOVE account can only result in difficulties for others wanting to be removed from our mailing list. This message is not intended for residents of the states of CALIFORNIA, COLORADO, ILLINOIS, NEVADA, OKLAHOMA, WASHINGTON and WEST VIRGINIA, and wherever else prohibited by law. Screening of addresses to avoid sending this e-mail to residents of these states has been done to the best of our technical ability. IT IS THE SOLE RESPONSIBILITY OF THE PURCHASER TO COMPLY WITH ALL APPLICABLE LOCAL, STATE AND FEDERAL LAWS IN ALL JURISDICTIONS. WE MAKE ABSOLUTELY NO CLAIMS, WARRANTIES OR REPRESENTATIONS REGARDING THE SUCCESS, POTENTIAL PROFITS OR ANY OTHER ACTUAL RESULTS FROM THE USE OF ANY MATERIAL ON THE CD, OR THE SECURITY, SAFETY, PERMISSIBILITY OR ADVISABILITY OF BULK EMAILING TO THE EMAIL ADDRESSES CONTAINED ON THE CD. The CD(s) you will receive come with a license agreement. By breaking the seal on the CD case(s) you will be agreeing to all of the terms and conditions of such license agreement. Once opened the CD(s) may not be returned; however, if found defective the CD(s) will be replaced at no charge. ************************************************************************ ***************************************************************************** 9947

3 2