http://web.irtnog.org/Members/xenophon/plone/portlet-folder-contents
This folder listing portlet displays the title of the folder, its
description, and a list of each item in the folder. Mousing over each
link pops up its description in browsers that understand the title
anchor (A) tag
-Original Message-
From: David Convent [mailto:[EMAIL PROTECTED]
Sent: Friday, April 01, 2005 3:30 AM
Plone now uses catalog queries to build folder listings, it avoids
waking up all objects and slow down the server response.
Consider using it, your portlet as it is written now can
My Zope server is currently an Alpha running FreeBSD. This computer's
CPU is no longer working. I would like to restore my backup copy of
Data.fs to a new computer, a PC running FreeBSD. Will this work as a
straightforward copy, or will the two platform's differing byte orders
(and word sizes)
Jens wrote:
There is no answer to this question because it cannot be answered.
No one has come against a limit yet as far as I know. Hitting RAM
limits depends on the settings you apply to the Zope/ZEO instance(s)
that serve(s) the content and how much RAM you put in, you can
control ZODB
I would recommend sticking to Linux, as this is the most
well-tested Zope platform. Python on *BSD has historically
had issues, don't know if that's still the case.
I'm running Zope and Plone on FreeBSD, both on i386 and alpha platforms.
I seem to have problems no one else experiences (like
Is it possible to export an object from a Zope instance in such a way
that, upon importing the object in a completely different Zope instance
and assuming the two Zope instances share a common authentication source
(e.g. LDAP), the original owner of the object is preserved? I want to
migrate key
(This is in regards to a post of mine from last year, i.e. http://mail.zope.org/pipermail/zope/2005-March/157400.html.)
Sir,
I received your email, but I am very sorry that I do not have time to reply in detail. In short, no, Zope will consume all available CPU cycles after some amount of
You can use Florent's DeadlockDebugger to find out what happens.
This is true for someone with the requisite skills and plenty of time.
In my case, the actual deadlock happens in a system library routine
(sigaction, as I recall), making the identification of the component
that's actually at
I thought a recent operating system upgrade (FreeBSD 5.4 to 6.1) fixed
my problems with Zope. Unfortunately, once I re-compiled Python et al
(to remove dependencies on the old libraries), my problems with Zope
deadlocking recurred. I tried to use a combination of tools to try to
discover the
be mainlining the hard stuff like trade agreements.
jsoffron: Too late...I've been freebasing Nafta all day... Sweet,
sweet NAFTA.
- As seen on Slashdot
-Original Message-
From: Dieter Maurer [mailto:[EMAIL PROTECTED]
Sent: Friday, June 16, 2006 2:36 PM
To: Matthew X. Economou
Cc
This time, when it locked, I thought to try a backtrace.
(gdb) info threads
* 7 LWP 100098 0x2820e544 in pthread_mutexattr_init () from
/usr/lib/libpthread.so.2
6 Thread 0x8111000 (sleeping) 0x2820df0f in pthread_mutexattr_init ()
from /usr/lib/libpthread.so.2
5 Thread 0xa1e1a00 (LWP
From: Dieter Maurer [mailto:[EMAIL PROTECTED]
I fear that you can call Python functions in general only on
the current thread (the other's probably lack the GIL,
an essential requirement to execute Python code).
Well, I upgraded to Python 2.4, re-compiled Zope and friends, and
updated a few
Praful,
Quills (a webblog Product for Zope/Plone) works something like that.
Perhaps you should take a look through its source code for clues as how
to implement your archival mechanism?
Best wishes,
Matthew
--
Rogues are very keen in their profession, and know already much
more than we can
I have a very simple script that copies my production Zope instance to
a fresh test instance. I have some Python code that I need to execute
when the test instance starts for the first time (it only needs to
execute once, but it won't hurt Zope if it executes every time the
test instance starts.
14 matches
Mail list logo
