Re: [Zope-dev] still segfaults, this time no ZMySQLDA

2002-02-28 Thread Matthew T. Kromer


On Wednesday, February 27, 2002, at 06:49 PM, Leonardo Rochael Almeida 
wrote:

 So, what should I try now?


Did -t 1 help?  If not, do you feel comfortable hooking up gdb  and 
getting a traceback?


___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope )



[Zope-dev] Zope 2.6 planning - call for contributors!

2002-02-28 Thread Brian Lloyd

Hi all - 

Paul sent a note to zope-coders some time back fishing for 
some feedback regarding planning for a Zope 2.6 (excepted):

 I propose that planning for a 2.6 focus on the following thoughts:
 
 1) This release is more about community-contributed work than 
 ZC-contributed work.
 ...
 
 Ultimately the things that go in 2.6 will be governed by what people in 
 the community are willing to contribute.
 
 So far the extent of contributions has been minor.  Do we need to widen 
 the pool?  Or do we instead try to get new contributors on the 
 Zope3 track?

There wasn't much response to this when it was originally posted. 
Now that 2.5.1 is nearly out the door, it's time to start planning 
for a Zope 2.6. I've started a 2.6 plan on the dev site at:

http://dev.zope.org/Resources/zope_260_plan.html

I wholeheartedly agree that 2.6 needs to be significantly a community 
effort. While I know that many people are engaged in the Zope 3 effort, 
we also need to get some people engaged on defining and producing 
2.6 in the interim. There is not much on the plan right now, so the 
possibilities are relatively wide open :) Let's get a discussion 
started to define 2.6.

Brian Lloyd[EMAIL PROTECTED]
Software Engineer  540.361.1716   
Zope Corporation   http://www.zope.com


___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope )



Re: [Zope-dev] FieldIndex unindex_object could not remove... This should not happen.

2002-02-28 Thread Andreas Jung

what zope version ?

- aj
- Original Message -
From: Florent Guillaume [EMAIL PROTECTED]
Newsgroups: local.lists.zope.zope-dev
To: [EMAIL PROTECTED]
Sent: Thursday, February 28, 2002 13:45
Subject: [Zope-dev] FieldIndex unindex_object could not remove... This
should not happen.


 Playing with workflow switching in CMF, I sometimes have this message:

 2002-02-28T18:33:06 ERROR(200) FieldIndex unindex_object could not remove
documentId -862940561 from index review_state.  This should not happen.
 Traceback (innermost last):
   File
/home/zope/test-zope/lib/python/Products/PluginIndexes/common/UnIndex.py,
line 168, in removeForwardIndexEntry
 (Object: review_state)
 KeyError: -862940561

 I gather that this happens when I do self.unindexObject() on an object
 that had a review_state attribute (actually a workflow variable made
 available to the catalog through a wrapper) in the past (being in a
 reviewing workflow) but at the time of the unindexing this variable does
 not existe anymore because the current workflow followed by the object
 doesn't have it.

 Does this ring any bell ?

 Thanks,

 Florent

 --
 Florent Guillaume, Nuxeo (Paris, France)
 +33 1 40 33 79 10  http://nuxeo.com  mailto:[EMAIL PROTECTED]

 ___
 Zope-Dev maillist  -  [EMAIL PROTECTED]
 http://lists.zope.org/mailman/listinfo/zope-dev
 **  No cross posts or HTML encoding!  **
 (Related lists -
  http://lists.zope.org/mailman/listinfo/zope-announce
  http://lists.zope.org/mailman/listinfo/zope )



___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope )



Re: [Zope-dev] still segfaults, this time no ZMySQLDA

2002-02-28 Thread Leonardo Rochael Almeida

On Thu, 2002-02-28 at 10:55, Matthew T. Kromer wrote:
 
 On Wednesday, February 27, 2002, at 06:49 PM, Leonardo Rochael Almeida 
 wrote:
 
  So, what should I try now?
 
 
 Did -t 1 help?  If not, do you feel comfortable hooking up gdb  and 
 getting a traceback?

Funny enough, running with -t 1 solved it.

/me starts looking sideways to ZMySQLDA again, since it's not the new
beta version...

The performance, understandably, is not the greatest, but it's tolerable
(where tolerable means the client hasn't complained yet).

I'll start looking at ways to recompile my python scripts using another
ZEO Client. I think I'll catalog all of them (using a very small
subtransaction threshould) and use a REQUEST.write() in a PyScript to
list them.

-- 
Ideas don't stay in some minds very long because they don't like
solitary confinement.


___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope )



Re: [Zope-dev] still segfaults, this time no ZMySQLDA

2002-02-28 Thread Matthew T. Kromer


On Thursday, February 28, 2002, at 02:09 PM, Leonardo Rochael Almeida 
wrote:

 Funny enough, running with -t 1 solved it.

 /me starts looking sideways to ZMySQLDA again, since it's not the new
 beta version...


Good!

Based on the fact that I'm not being innundated with I'm still 
crashing! complaints, I'm going to *guess* that -t 1 isolated the bad 
module, which was probably being activated even though you didn't think 
it was.  Maybe something traversed to it, or activated it in some other 
way.

I don't think there is a thread-sensitive gremlin in Zope 2.5, but I'm 
asking all parties to keep an eye open for a vanilla 2.5 (or 2.4.4) 
crash that -t 1 solves.


___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope )



Re: [Zope-dev] still segfaults, this time no ZMySQLDA

2002-02-28 Thread Leonardo Rochael Almeida

On Thu, 2002-02-28 at 16:09, Leonardo Rochael Almeida wrote:
 On Thu, 2002-02-28 at 10:55, Matthew T. Kromer wrote:
  
  On Wednesday, February 27, 2002, at 06:49 PM, Leonardo Rochael Almeida 
  wrote:
  
   So, what should I try now?
  
  
  Did -t 1 help?  If not, do you feel comfortable hooking up gdb  and 
  getting a traceback?
 
 Funny enough, running with -t 1 solved it.
 
 /me starts looking sideways to ZMySQLDA again, since it's not the new
 beta version...
 
 The performance, understandably, is not the greatest, but it's tolerable
 (where tolerable means the client hasn't complained yet).
 
 I'll start looking at ways to recompile my python scripts using another
 ZEO Client. I think I'll catalog all of them (using a very small
 subtransaction threshould) and use a REQUEST.write() in a PyScript to
 list them.
 

COOL!!

I found a kickass way to recompile all PythonScripts without bringing
down the machine and writing the least amount of code ever possible!

Short version:

Create a python script in Zope root that recompiles context and
catalog all python scripts using that as a metadata.

Long version:

put the following python script in your root:
=
## Script (Python) recompile
##bind container=container
##bind context=context
##bind namespace=
##bind script=script
##bind subpath=traverse_subpath
##parameters=
##title=
##
# recompile the thing
context.write(context.read())

# return something to waste catalog space :-)
from string import join
return recompiled %s\n % join(context.getPhysicalPath(),/)
=

Now put a ZCatalog in your root, call it anything, say, pyScripts. Go to
the Indexex tab and remove all indexes but the path index. Go back
and go to the Metadata tab; remove all metadata and insert recompile
and getPhysicalPath (this one is completely optional). Go to the
Advanced tab and set the subtransaction threshould to a number that
looks reasonable to you (low enough so as not to  crash your machine
:-). Go to the Find Objects tab, make sure that only Script (Python)
is selected (verify, especially, that All types isn't selected) and
click Find and Catalog.

wait...

wait...

wait some more...

go get a coke or a coffee or something...

wait a little more...

When you see the result page, you know that your pythonScripts are
recompiled (of course it won't take that long unless you have an 800+MiB
Data.fs crammed full of python scripts :-)

Cheers, Leo

-- 
Ideas don't stay in some minds very long because they don't like
solitary confinement.


___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope )



Re: [Zope-dev] FieldIndex unindex_object could not remove... This should not happen.

2002-02-28 Thread Florent Guillaume

2.5.0 linux binary release, sorry.

Andreas Jung [EMAIL PROTECTED] wrote:
 what zope version ?
 
 - aj
 - Original Message -
 From: Florent Guillaume [EMAIL PROTECTED]
 Newsgroups: local.lists.zope.zope-dev
 To: [EMAIL PROTECTED]
 Sent: Thursday, February 28, 2002 13:45
 Subject: [Zope-dev] FieldIndex unindex_object could not remove... This
 should not happen.
 
 
  Playing with workflow switching in CMF, I sometimes have this message:
 
  2002-02-28T18:33:06 ERROR(200) FieldIndex unindex_object could not remove
 documentId -862940561 from index review_state.  This should not happen.
  Traceback (innermost last):
File
 /home/zope/test-zope/lib/python/Products/PluginIndexes/common/UnIndex.py,
 line 168, in removeForwardIndexEntry
  (Object: review_state)
  KeyError: -862940561
 
  I gather that this happens when I do self.unindexObject() on an object
  that had a review_state attribute (actually a workflow variable made
  available to the catalog through a wrapper) in the past (being in a
  reviewing workflow) but at the time of the unindexing this variable does
  not existe anymore because the current workflow followed by the object
  doesn't have it.
 
  Does this ring any bell ?
 
  Thanks,
 
  Florent
 
  --
  Florent Guillaume, Nuxeo (Paris, France)
  +33 1 40 33 79 10  http://nuxeo.com  mailto:[EMAIL PROTECTED]
 
  ___
  Zope-Dev maillist  -  [EMAIL PROTECTED]
  http://lists.zope.org/mailman/listinfo/zope-dev
  **  No cross posts or HTML encoding!  **
  (Related lists -
   http://lists.zope.org/mailman/listinfo/zope-announce
   http://lists.zope.org/mailman/listinfo/zope )
 
 
 
 ___
 Zope-Dev maillist  -  [EMAIL PROTECTED]
 http://lists.zope.org/mailman/listinfo/zope-dev
 **  No cross posts or HTML encoding!  **
 (Related lists - 
  http://lists.zope.org/mailman/listinfo/zope-announce
  http://lists.zope.org/mailman/listinfo/zope )
 


-- 
Florent Guillaume, Nuxeo (Paris, France)
+33 1 40 33 79 10  http://nuxeo.com  mailto:[EMAIL PROTECTED]

___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope )



Re: [Zope-dev] FieldIndex unindex_object could not remove... This should not happen.

2002-02-28 Thread Florent Guillaume

Ok forget about it, I was unindexing and indexing from several catalogs,
and mixed some of them up. All is well now.
(However the message was still strange...)

Florent


Florent Guillaume  [EMAIL PROTECTED] wrote:
 2.5.0 linux binary release, sorry.
 
 Andreas Jung [EMAIL PROTECTED] wrote:
  what zope version ?
  
  - aj
  - Original Message -
  From: Florent Guillaume [EMAIL PROTECTED]
  Newsgroups: local.lists.zope.zope-dev
  To: [EMAIL PROTECTED]
  Sent: Thursday, February 28, 2002 13:45
  Subject: [Zope-dev] FieldIndex unindex_object could not remove... This
  should not happen.
  
  
   Playing with workflow switching in CMF, I sometimes have this message:
  
   2002-02-28T18:33:06 ERROR(200) FieldIndex unindex_object could not remove
  documentId -862940561 from index review_state.  This should not happen.
   Traceback (innermost last):
 File
  /home/zope/test-zope/lib/python/Products/PluginIndexes/common/UnIndex.py,
  line 168, in removeForwardIndexEntry
   (Object: review_state)
   KeyError: -862940561
  
   I gather that this happens when I do self.unindexObject() on an object
   that had a review_state attribute (actually a workflow variable made
   available to the catalog through a wrapper) in the past (being in a
   reviewing workflow) but at the time of the unindexing this variable does
   not existe anymore because the current workflow followed by the object
   doesn't have it.
  
   Does this ring any bell ?
  
   Thanks,
  
   Florent
-- 
Florent Guillaume, Nuxeo (Paris, France)
+33 1 40 33 79 10  http://nuxeo.com  mailto:[EMAIL PROTECTED]

___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope )



Re: [Zope-dev] FieldIndex unindex_object could not remove... This should not happen.

2002-02-28 Thread Andreas Jung

Well...that should not happen :-)
Maybe try the check_catalog.py script from Zope 2.5.X
to find any problems in the indexes.

Andreas
- Original Message -
From: Florent Guillaume [EMAIL PROTECTED]
Newsgroups: local.lists.zope.zope-dev
To: [EMAIL PROTECTED]
Sent: Thursday, February 28, 2002 15:57
Subject: Re: [Zope-dev] FieldIndex unindex_object could not remove... This
should not happen.


 Ok forget about it, I was unindexing and indexing from several catalogs,
 and mixed some of them up. All is well now.
 (However the message was still strange...)

 Florent


 Florent Guillaume  [EMAIL PROTECTED] wrote:
  2.5.0 linux binary release, sorry.
 
  Andreas Jung [EMAIL PROTECTED] wrote:
   what zope version ?
  
   - aj
   - Original Message -
   From: Florent Guillaume [EMAIL PROTECTED]
   Newsgroups: local.lists.zope.zope-dev
   To: [EMAIL PROTECTED]
   Sent: Thursday, February 28, 2002 13:45
   Subject: [Zope-dev] FieldIndex unindex_object could not remove... This
   should not happen.
  
  
Playing with workflow switching in CMF, I sometimes have this
message:
   
2002-02-28T18:33:06 ERROR(200) FieldIndex unindex_object could not
remove
   documentId -862940561 from index review_state.  This should not
happen.
Traceback (innermost last):
  File
  
/home/zope/test-zope/lib/python/Products/PluginIndexes/common/UnIndex.py,
   line 168, in removeForwardIndexEntry
(Object: review_state)
KeyError: -862940561
   
I gather that this happens when I do self.unindexObject() on an
object
that had a review_state attribute (actually a workflow variable made
available to the catalog through a wrapper) in the past (being in a
reviewing workflow) but at the time of the unindexing this variable
does
not existe anymore because the current workflow followed by the
object
doesn't have it.
   
Does this ring any bell ?
   
Thanks,
   
Florent
 --
 Florent Guillaume, Nuxeo (Paris, France)
 +33 1 40 33 79 10  http://nuxeo.com  mailto:[EMAIL PROTECTED]

 ___
 Zope-Dev maillist  -  [EMAIL PROTECTED]
 http://lists.zope.org/mailman/listinfo/zope-dev
 **  No cross posts or HTML encoding!  **
 (Related lists -
  http://lists.zope.org/mailman/listinfo/zope-announce
  http://lists.zope.org/mailman/listinfo/zope )



___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope )



Re: [Zope-dev] Zope 2.6 planning - call for contributors!

2002-02-28 Thread Behrens Matt - Grand Rapids

Brian Lloyd wrote:

  Let's get a discussion
 started to define 2.6.

This isn't exciting by any means unless you're one of the people who 
package Zope up for distribution, or maybe you're one of the people who 
manage lots of little Zopes on one system; but I'd like to revive the 
grand unified Zope installation and control proposal that has been 
floated by many people (including me) in one form or another for some 
time.  Wikiwise, this would wrap up
http://dev.zope.org/Wikis/DevSite/Proposals/ZopeStartupProvisions and 
http://dev.zope.org/Wikis/DevSite/Proposals/InstallationAndConfiguration, 
at least.

To summarize, this would involve

- an expanded build program with an installation scheme that would allow 
multiple versions of Zope to be present on the same system

- making that installation 'secure by default'

- a registry of Zope installations and one of instances and their 
configuration settings

- a 'zopectl' program or similar that would be able to start and stop 
instances

- a 'zopeinstance' program or similar that would become the 
_recommended_ way of setting up Zope, by creating an INSTANCE_HOME

It would be nice if

- the same framework could apply to Zope 3, maybe taking care of that 
piece ahead of time

I'm more than willing to head this up, though I question how long we 
have before 2.6 to do so.

___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope )



Re: [Zope-dev] FieldIndex unindex_object could not remove... This should not happen.

2002-02-28 Thread Florent Guillaume

Both catalogs were ok.

BTW this patch is needed:
--- check_catalog.pyThu Feb 28 22:13:30 2002
+++ check_catalog.pyThu Feb 28 22:23:15 2002
@@ -140,7 +140,7 @@
 if o in ['--FieldIndex','--KeywordIndex','--PathIndex']:
 indexes.append(o[2:])

-checkCatalog(args,indexes)
+checkCatalog(args[0],indexes)


 if __name__=='__main__':




Andreas Jung [EMAIL PROTECTED] wrote:
 Well...that should not happen :-)
 Maybe try the check_catalog.py script from Zope 2.5.X
 to find any problems in the indexes.
 
 Andreas
 - Original Message -
 From: Florent Guillaume [EMAIL PROTECTED]
 Newsgroups: local.lists.zope.zope-dev
 To: [EMAIL PROTECTED]
 Sent: Thursday, February 28, 2002 15:57
 Subject: Re: [Zope-dev] FieldIndex unindex_object could not remove... This
 should not happen.
 
 
  Ok forget about it, I was unindexing and indexing from several catalogs,
  and mixed some of them up. All is well now.
  (However the message was still strange...)
 
  Florent
 
 
  Florent Guillaume  [EMAIL PROTECTED] wrote:
   2.5.0 linux binary release, sorry.
  
   Andreas Jung [EMAIL PROTECTED] wrote:
what zope version ?
   
- aj
- Original Message -
From: Florent Guillaume [EMAIL PROTECTED]
Newsgroups: local.lists.zope.zope-dev
To: [EMAIL PROTECTED]
Sent: Thursday, February 28, 2002 13:45
Subject: [Zope-dev] FieldIndex unindex_object could not remove... This
should not happen.
   
   
 Playing with workflow switching in CMF, I sometimes have this
 message:

 2002-02-28T18:33:06 ERROR(200) FieldIndex unindex_object could not
 remove
documentId -862940561 from index review_state.  This should not
 happen.
 Traceback (innermost last):
   File
   
 /home/zope/test-zope/lib/python/Products/PluginIndexes/common/UnIndex.py,
line 168, in removeForwardIndexEntry
 (Object: review_state)
 KeyError: -862940561

 I gather that this happens when I do self.unindexObject() on an
 object
 that had a review_state attribute (actually a workflow variable made
 available to the catalog through a wrapper) in the past (being in a
 reviewing workflow) but at the time of the unindexing this variable
 does
 not existe anymore because the current workflow followed by the
 object
 doesn't have it.

 Does this ring any bell ?

 Thanks,

 Florent
  --
  Florent Guillaume, Nuxeo (Paris, France)
  +33 1 40 33 79 10  http://nuxeo.com  mailto:[EMAIL PROTECTED]
 
  ___
  Zope-Dev maillist  -  [EMAIL PROTECTED]
  http://lists.zope.org/mailman/listinfo/zope-dev
  **  No cross posts or HTML encoding!  **
  (Related lists -
   http://lists.zope.org/mailman/listinfo/zope-announce
   http://lists.zope.org/mailman/listinfo/zope )
 
 
 
 ___
 Zope-Dev maillist  -  [EMAIL PROTECTED]
 http://lists.zope.org/mailman/listinfo/zope-dev
 **  No cross posts or HTML encoding!  **
 (Related lists - 
  http://lists.zope.org/mailman/listinfo/zope-announce
  http://lists.zope.org/mailman/listinfo/zope )
 


-- 
Florent Guillaume, Nuxeo (Paris, France)
+33 1 40 33 79 10  http://nuxeo.com  mailto:[EMAIL PROTECTED]

___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope )



Re: [Zope-Coders] Re: [Zope-dev] Zope 2.6 planning - call for contributors!

2002-02-28 Thread Casey Duncan

On Thursday 28 February 2002 04:03 pm, you wrote:
 Brian Lloyd wrote:
   Let's get a discussion
 
  started to define 2.6.

 This isn't exciting by any means unless you're one of the people who
 package Zope up for distribution, or maybe you're one of the people who
 manage lots of little Zopes on one system; but I'd like to revive the
 grand unified Zope installation and control proposal that has been
 floated by many people (including me) in one form or another for some
 time.  Wikiwise, this would wrap up
 http://dev.zope.org/Wikis/DevSite/Proposals/ZopeStartupProvisions and
 http://dev.zope.org/Wikis/DevSite/Proposals/InstallationAndConfiguration,
 at least.

 To summarize, this would involve

 - an expanded build program with an installation scheme that would allow
 multiple versions of Zope to be present on the same system

+1

I just did this manually yesterday and it would be *really* nice to have it 
work like this out of the box. I think it would really improve first 
impressions of Zope from a site admin perspective.

/---\
  Casey Duncan, Sr. Web Developer
  National Legal Aid and Defender Association
  [EMAIL PROTECTED]
\---/

___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope )



Re: [Zope-dev] still segfaults, this time no ZMySQLDA

2002-02-28 Thread Casey Duncan

On Thursday 28 February 2002 02:51 pm, Leonardo Rochael Almeida allegedly 
wrote:
[snip]
 When you see the result page, you know that your pythonScripts are
 recompiled (of course it won't take that long unless you have an 800+MiB
 Data.fs crammed full of python scripts :-)

 Cheers, Leo

I hope those weren't all coded in a textarea 8*). Ouch.

/---\
  Casey Duncan, Sr. Web Developer
  National Legal Aid and Defender Association
  [EMAIL PROTECTED]
\---/

___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope )



[Zope-dev] improved logging

2002-02-28 Thread Romain Slootmaekers


Yo,
questions wrt logging:

-) What are the plans to improve the rather primitive logging facilities
in zope ?
I couldn't find anything in the plan for 2.6, nor on the 3.0 homepage.
I think we need at least an extendibl framework with following types of
components:

- Loggers (fi, file logger, db loggers, remote logger, nulllogger,...)
- Filters (fi on severity, on subsystem, ...)
- LogBus (central accesspoint for the logging framework,
  where you can (dynamically) hook your loggers, filters etc...

if time is an issue, we could just copy the design of fi Log4J which is a
good logging framework for apache.
 
-) If there are no such plans, can we hack something up ourselves and
add/donate it to the product ? I hate writing stuff that gets replaced by
something else afterwards 

input appreciated.

Sloot.
 







___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope )



Re: [Zope-dev] Zope 2.6 planning - call for contributors!

2002-02-28 Thread Chris McDonough

 I've modified HTTPResponse and ZServer/HTTPResponse.py to allow for gzip
content
 encoding on a response-by-response basis.  I'm mostly using this with
xml-rpc, but it
 could be generalized and combined with a gzipper- cache manager.

I'd like this.  It would help with the lack of transfer-encoding by Squid.


___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope )



Re: [Zope-dev] improved logging

2002-02-28 Thread John Ziniti

http://freshmeat.net/projects/log4py/


Romain Slootmaekers wrote:
 Yo,
 questions wrt logging:
 
 -) What are the plans to improve the rather primitive logging facilities
 in zope ?
 I couldn't find anything in the plan for 2.6, nor on the 3.0 homepage.
 I think we need at least an extendibl framework with following types of
 components:
 
 - Loggers (fi, file logger, db loggers, remote logger, nulllogger,...)
 - Filters (fi on severity, on subsystem, ...)
 - LogBus (central accesspoint for the logging framework,
   where you can (dynamically) hook your loggers, filters etc...
 
 if time is an issue, we could just copy the design of fi Log4J which is a
 good logging framework for apache.
  
 -) If there are no such plans, can we hack something up ourselves and
 add/donate it to the product ? I hate writing stuff that gets replaced by
 something else afterwards 
 
 input appreciated.
 
 Sloot.
  
 
 
 
 
 
 
 
 ___
 Zope-Dev maillist  -  [EMAIL PROTECTED]
 http://lists.zope.org/mailman/listinfo/zope-dev
 **  No cross posts or HTML encoding!  **
 (Related lists - 
  http://lists.zope.org/mailman/listinfo/zope-announce
  http://lists.zope.org/mailman/listinfo/zope )
 
 
 



___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope )



[Zope-dev] Online BTrees documentation released

2002-02-28 Thread Andreas Jung

FYI,

I have set up a Wiki that should provide a usable documentation
of the Zopes BTrees package. The Wiki is still evolving but it
explains (hopefully) the most important datatypes, their API
and other helper functions.

URL:
  http://www.zope.org/Members/ajung/BTrees/FrontPage

Cheers,
Andreas

-
   -Andreas JungZope Corporation   -
  -   EMail: [EMAIL PROTECTED]http://www.zope.com  -
 -  Python Powered   http://www.python.org - 
  -   Makers of Zope   http://www.zope.org  - 
   -Life is too short to (re)write parsers   -
-




___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope )



RE: [Zope-dev] Zope 2.6 planning - call for contributors!

2002-02-28 Thread sean . upton

Hmm... would this still work with Squid or Apache caching in front of Zope?


I assume that since each browser can accept different transfer-encodings,
this has to be done as close to the browser as possible, otherwise content
sent in one transfer encoding would be sent to every user if it was to be
cached (in other words, instead this would have to be done using the
experimental Squid TE code)...

Sean

-Original Message-
From: Chris McDonough [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 28, 2002 2:36 PM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: [Zope-dev] Zope 2.6 planning - call for contributors!


 I've modified HTTPResponse and ZServer/HTTPResponse.py to allow for gzip
content
 encoding on a response-by-response basis.  I'm mostly using this with
xml-rpc, but it
 could be generalized and combined with a gzipper- cache manager.

I'd like this.  It would help with the lack of transfer-encoding by Squid.


___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope )

___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope )



Re: [Zope-dev] Zope 2.6 planning - call for contributors!

2002-02-28 Thread John Ziniti

   Let's get a discussion
 
  started to define 2.6
 

I'd like to see the ZSyncer Product, or a variant thereof, included in
Zope by default.  That is, I'd like Synchronization, to a be a default
property of Zope objects, so that objects/content can be pushed and
pulled between two Zope installations.

I venture a guess that the development/production model is common,
and this helps quite a bit in maintaining this model.

Ziniti



___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope )



Re: [Zope-dev] Zope 2.6 planning - call for contributors!

2002-02-28 Thread Eric Roby




   Let's get a discussion
  
   started to define 2.6
  

 I'd like to see the ZSyncer Product, or a variant thereof, included in
 Zope by default.  That is, I'd like Synchronization, to a be a default
 property of Zope objects, so that objects/content can be pushed and
 pulled between two Zope installations.

 I venture a guess that the development/production model is common,
 and this helps quite a bit in maintaining this model.

 Ziniti


Absolutely ... and I would also like to see Richards excellent Call Profiler
service become part of the core.  It is an (absolutely) essential tool for a
number of reasons.  My impression from previous threads is that others feel
the same way too.  I would also like to know what level of effort it would
take to ramp-up transparent folders so that it could be considered core
ready???  Anyway, my two cents...

Eric

___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope )



Re: [Zope-dev] Zope 2.6 planning - call for contributors!

2002-02-28 Thread Richard Jones

On Fri, 1 Mar 2002 15:17, Eric Roby wrote:
Let's get a discussion
   
started to define 2.6
 
  I'd like to see the ZSyncer Product, or a variant thereof, included in
  Zope by default.  That is, I'd like Synchronization, to a be a default
  property of Zope objects, so that objects/content can be pushed and
  pulled between two Zope installations.
 
  I venture a guess that the development/production model is common,
  and this helps quite a bit in maintaining this model.
 
  Ziniti

 Absolutely ... and I would also like to see Richards excellent Call
 Profiler service become part of the core.

I'm definitely putting the profiler into 2.6 - there's just an open question 
of where it gets put. The question was asked on zope-coders, and got no 
response. I figure if no-one answers within a week of my original posting, 
I'll just check it in as a product.


Richard


___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope )



Re: [Zope-dev] Zope 2.6 planning - call for contributors!

2002-02-28 Thread Andre Schubert

Hi,

John Ziniti schrieb:
 
Let's get a discussion
  
   started to define 2.6
  
 
 I'd like to see the ZSyncer Product, or a variant thereof, included in
 Zope by default.  That is, I'd like Synchronization, to a be a default
 property of Zope objects, so that objects/content can be pushed and
 pulled between two Zope installations.

I would use ZCVSFolder or somewhat likely that included instead of
ZSyncer.
The problem i see is that we have a development server and more than one
production instances in our organisation.
If a product comes out of its development state it is moved to the
production server.
If you use ZSyncer then all Objects zsynced over all instances have
the same version, but if you use ZCVSFolder instead
then you have a version-control mechanism of all objects on the
different instances.

 
 I venture a guess that the development/production model is common,
 and this helps quite a bit in maintaining this model.
 
 Ziniti
 
 ___
 Zope-Dev maillist  -  [EMAIL PROTECTED]
 http://lists.zope.org/mailman/listinfo/zope-dev
 **  No cross posts or HTML encoding!  **
 (Related lists -
  http://lists.zope.org/mailman/listinfo/zope-announce
  http://lists.zope.org/mailman/listinfo/zope )

-- 
Andre SchubertEMail:   [EMAIL PROTECTED]
  Tel: 03774 6625-78
km3 teledienst GmbH   Fax: 03774 6625-79

___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope )



Re: [Zope-dev] Zope 2.6 planning - call for contributors!

2002-02-28 Thread Lennart Regebro

 I wholeheartedly agree that 2.6 needs to be significantly a community
 effort. While I know that many people are engaged in the Zope 3 effort,
 we also need to get some people engaged on defining and producing
 2.6 in the interim. There is not much on the plan right now, so the
 possibilities are relatively wide open :) Let's get a discussion
 started to define 2.6.

OK. The things I'd like to see included is the Enhanced Virtual Host Monster
that iMeme did, or maybe even the Virtual Host Folder that is being
developed now (I haven't tried that one out, but it looks good on paper).

I'd also like the functionality provided by the local roles blacklist
enhancement we did ( http://www.zope.org/Members/regebro/LRBlacklist ).

And of course, the bugs that we have reported fixed. :-)

Can't think of anything more right now.


___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope )