[Zope-Checkins] SVN: Zope/branches/2.9/ - Collector #1939: When running as a service, Zope could

[Sidnei da Silva]

Log message for revision 40951:
  
- Collector #1939: When running as a service, Zope could
  potentially collect too much log output filling the NT Event
  Log. When that happened, a 'print' during exception handling
  would cause an IOError in the restart code causing the service
  not to restart automatically.
  
  Problem is that a service/pythonw.exe process *always* has an
  invalid sys.stdout.  But due to the magic of buffering, small
  print statements would not fail - but once the file actually
  got written to, the error happened.  Never a problem when
  debugging, as the process has a console, and hence a valid
  stdout.
  

Changed:
  U   Zope/branches/2.9/doc/CHANGES.txt
  U   Zope/branches/2.9/lib/python/nt_svcutils/service.py

-=-
Modified: Zope/branches/2.9/doc/CHANGES.txt
===
--- Zope/branches/2.9/doc/CHANGES.txt   2005-12-21 12:15:36 UTC (rev 40950)
+++ Zope/branches/2.9/doc/CHANGES.txt   2005-12-21 12:29:35 UTC (rev 40951)
@@ -23,10 +23,23 @@
- Collector #1233: port ZOPE_CONFIG patch from Zope 2.7 to Zope 2.8
 
 
-  after Zope 2.9.0 beta 1 
+  after Zope 2.9.0 beta 1
 
 Bugs fixed
 
+  - Collector #1939: When running as a service, Zope could
+potentially collect too much log output filling the NT Event
+Log. When that happened, a 'print' during exception handling
+would cause an IOError in the restart code causing the service
+not to restart automatically.
+
+Problem is that a service/pythonw.exe process *always* has an
+invalid sys.stdout.  But due to the magic of buffering, small
+print statements would not fail - but once the file actually
+got written to, the error happened.  Never a problem when
+debugging, as the process has a console, and hence a valid
+stdout.
+
  - For content-type HTTP headers starting with 'text/' or 'application/'
the 'charset' field is automatically if not specified by the
application. The 'charset' is determined by the content-type header

Modified: Zope/branches/2.9/lib/python/nt_svcutils/service.py
===
--- Zope/branches/2.9/lib/python/nt_svcutils/service.py 2005-12-21 12:15:36 UTC 
(rev 40950)
+++ Zope/branches/2.9/lib/python/nt_svcutils/service.py 2005-12-21 12:29:35 UTC 
(rev 40951)
@@ -36,8 +36,10 @@
 # (except obviously via the event log entry)
 # Size of the blocks we read from the child process's output.
 CHILDCAPTURE_BLOCK_SIZE = 80
-# The number of BLOCKSIZE blocks we keep as process output.
-CHILDCAPTURE_MAX_BLOCKS = 200
+# The number of BLOCKSIZE blocks we keep as process output.  This gives
+# is 4k, which should be enough to see any tracebacks etc, but not so
+# large as to prematurely fill the event log.
+CHILDCAPTURE_MAX_BLOCKS = 50
 
 class Service(win32serviceutil.ServiceFramework):
 Base class for a Windows Server to manage an external process.
@@ -108,7 +110,10 @@
 except win32api.error, details:
 # Failed to write a log entry - most likely problem is
 # that the event log is full.  We don't want this to kill us
-print FAILED to write INFO event, event, :, details
+try:
+print FAILED to write INFO event, event, :, details
+except IOError:
+pass
 
 def _dolog(self, func, msg):
 try:
@@ -118,8 +123,13 @@
 except win32api.error, details:
 # Failed to write a log entry - most likely problem is
 # that the event log is full.  We don't want this to kill us
-print FAILED to write event log entry:, details
-print msg
+try:
+print FAILED to write event log entry:, details
+print msg
+except IOError:
+# And if running as a service, its likely our sys.stdout
+# is invalid
+pass
 
 def info(self, s):
 self._dolog(servicemanager.LogInfoMsg, s)

___
Zope-Checkins maillist  -  Zope-Checkins@zope.org
http://mail.zope.org/mailman/listinfo/zope-checkins

[Zope-Checkins] SVN: Zope/trunk/lib/python/ZPublisher/ fixes + more tests (Stefan Holek)

[Andreas Jung]

Log message for revision 40954:
  fixes + more tests (Stefan Holek)
  

Changed:
  U   Zope/trunk/lib/python/ZPublisher/HTTPResponse.py
  U   Zope/trunk/lib/python/ZPublisher/tests/testHTTPResponse.py

-=-
Modified: Zope/trunk/lib/python/ZPublisher/HTTPResponse.py
===
--- Zope/trunk/lib/python/ZPublisher/HTTPResponse.py2005-12-21 15:01:15 UTC 
(rev 40953)
+++ Zope/trunk/lib/python/ZPublisher/HTTPResponse.py2005-12-21 15:03:12 UTC 
(rev 40954)
@@ -333,13 +333,18 @@
 self.body = body
 
 
+isHTML = self.isHTML(self.body)
 if not self.headers.has_key('content-type'):
-isHTML = self.isHTML(self.body)
 if isHTML:
 c = 'text/html; charset=%s' % default_encoding
 else:
 c = 'text/plain; charset=%s' % default_encoding
 self.setHeader('content-type', c)
+else:
+c = self.headers['content-type']
+if not 'charset=' in  c:
+c = '%s; charset=%s' % (c, default_encoding)
+self.setHeader('content-type', c)
 
 # Some browsers interpret certain characters in Latin 1 as html
 # special characters. These cannot be removed by html_quote,

Modified: Zope/trunk/lib/python/ZPublisher/tests/testHTTPResponse.py
===
--- Zope/trunk/lib/python/ZPublisher/tests/testHTTPResponse.py  2005-12-21 
15:01:15 UTC (rev 40953)
+++ Zope/trunk/lib/python/ZPublisher/tests/testHTTPResponse.py  2005-12-21 
15:03:12 UTC (rev 40954)
@@ -74,7 +74,18 @@
 response.appendHeader('XXX', 'foo')
 self.assertEqual(response.headers.get('xxx'), 'bar,\n\tfoo')
 
+def test_CharsetNoHeader(self):
+response = self._makeOne(body='foo')
+self.assertEqual(response.headers.get('content-type'), 'text/plain; 
charset=iso-8859-15')
 
+def test_CharsetTextHeader(self):
+response = self._makeOne(body='foo', headers={'content-type': 
'text/plain'})
+self.assertEqual(response.headers.get('content-type'), 'text/plain; 
charset=iso-8859-15')
+
+def test_CharsetApplicationHeader(self):
+response = self._makeOne(body='foo', headers={'content-type': 
'application/foo'})
+self.assertEqual(response.headers.get('content-type'), 
'application/foo; charset=iso-8859-15')
+
 def test_suite():
 suite = unittest.TestSuite()
 suite.addTest(unittest.makeSuite(HTTPResponseTests, 'test'))

___
Zope-Checkins maillist  -  Zope-Checkins@zope.org
http://mail.zope.org/mailman/listinfo/zope-checkins

[Zope-Checkins] SVN: Zope/trunk/lib/python/ZPublisher/tests/testHTTPResponse.py more tests

[Andreas Jung]

Log message for revision 40955:
  more tests
  

Changed:
  U   Zope/trunk/lib/python/ZPublisher/tests/testHTTPResponse.py

-=-
Modified: Zope/trunk/lib/python/ZPublisher/tests/testHTTPResponse.py
===
--- Zope/trunk/lib/python/ZPublisher/tests/testHTTPResponse.py  2005-12-21 
15:03:12 UTC (rev 40954)
+++ Zope/trunk/lib/python/ZPublisher/tests/testHTTPResponse.py  2005-12-21 
15:09:16 UTC (rev 40955)
@@ -1,3 +1,5 @@
+# -*- coding: iso-8859-15 -*-
+
 import unittest
 
 class HTTPResponseTests(unittest.TestCase):
@@ -85,7 +87,17 @@
 def test_CharsetApplicationHeader(self):
 response = self._makeOne(body='foo', headers={'content-type': 
'application/foo'})
 self.assertEqual(response.headers.get('content-type'), 
'application/foo; charset=iso-8859-15')
+
+def test_CharsetApplicationHeaderUnicode(self):
+response = self._makeOne(body=unicode('ärger', 'iso-8859-15'), 
headers={'content-type': 'application/foo'})
+self.assertEqual(response.headers.get('content-type'), 
'application/foo; charset=iso-8859-15')
+self.assertEqual(response.body, 'ärger')
 
+def test_CharsetApplicationHeader1Unicode(self):
+response = self._makeOne(body=unicode('ärger', 'iso-8859-15'), 
headers={'content-type': 'application/foo; charset=utf-8'})
+self.assertEqual(response.headers.get('content-type'), 
'application/foo; charset=utf-8')
+self.assertEqual(response.body, unicode('ärger', 
'iso-8859-15').encode('utf-8'))
+
 def test_suite():
 suite = unittest.TestSuite()
 suite.addTest(unittest.makeSuite(HTTPResponseTests, 'test'))

___
Zope-Checkins maillist  -  Zope-Checkins@zope.org
http://mail.zope.org/mailman/listinfo/zope-checkins

[Zope-Checkins] SVN: Zope/branches/2.9/lib/python/ZPublisher/ more tests and fixes

[Andreas Jung]

Log message for revision 40956:
  more tests and fixes
  

Changed:
  U   Zope/branches/2.9/lib/python/ZPublisher/HTTPResponse.py
  U   Zope/branches/2.9/lib/python/ZPublisher/tests/testHTTPResponse.py

-=-
Modified: Zope/branches/2.9/lib/python/ZPublisher/HTTPResponse.py
===
--- Zope/branches/2.9/lib/python/ZPublisher/HTTPResponse.py 2005-12-21 
15:09:16 UTC (rev 40955)
+++ Zope/branches/2.9/lib/python/ZPublisher/HTTPResponse.py 2005-12-21 
15:12:00 UTC (rev 40956)
@@ -333,13 +333,18 @@
 self.body = body
 
 
+isHTML = self.isHTML(self.body)
 if not self.headers.has_key('content-type'):
-isHTML = self.isHTML(self.body)
 if isHTML:
 c = 'text/html; charset=%s' % default_encoding
 else:
 c = 'text/plain; charset=%s' % default_encoding
 self.setHeader('content-type', c)
+else:
+c = self.headers['content-type']
+if not 'charset=' in  c:
+c = '%s; charset=%s' % (c, default_encoding)
+self.setHeader('content-type', c)
 
 # Some browsers interpret certain characters in Latin 1 as html
 # special characters. These cannot be removed by html_quote,

Modified: Zope/branches/2.9/lib/python/ZPublisher/tests/testHTTPResponse.py
===
--- Zope/branches/2.9/lib/python/ZPublisher/tests/testHTTPResponse.py   
2005-12-21 15:09:16 UTC (rev 40955)
+++ Zope/branches/2.9/lib/python/ZPublisher/tests/testHTTPResponse.py   
2005-12-21 15:12:00 UTC (rev 40956)
@@ -1,3 +1,5 @@
+# -*- coding: iso-8859-15 -*-
+
 import unittest
 
 class HTTPResponseTests(unittest.TestCase):
@@ -74,7 +76,28 @@
 response.appendHeader('XXX', 'foo')
 self.assertEqual(response.headers.get('xxx'), 'bar,\n\tfoo')
 
+def test_CharsetNoHeader(self):
+response = self._makeOne(body='foo')
+self.assertEqual(response.headers.get('content-type'), 'text/plain; 
charset=iso-8859-15')
 
+def test_CharsetTextHeader(self):
+response = self._makeOne(body='foo', headers={'content-type': 
'text/plain'})
+self.assertEqual(response.headers.get('content-type'), 'text/plain; 
charset=iso-8859-15')
+
+def test_CharsetApplicationHeader(self):
+response = self._makeOne(body='foo', headers={'content-type': 
'application/foo'})
+self.assertEqual(response.headers.get('content-type'), 
'application/foo; charset=iso-8859-15')
+
+def test_CharsetApplicationHeaderUnicode(self):
+response = self._makeOne(body=unicode('ärger', 'iso-8859-15'), 
headers={'content-type': 'application/foo'})
+self.assertEqual(response.headers.get('content-type'), 
'application/foo; charset=iso-8859-15')
+self.assertEqual(response.body, 'ärger')
+
+def test_CharsetApplicationHeader1Unicode(self):
+response = self._makeOne(body=unicode('ärger', 'iso-8859-15'), 
headers={'content-type': 'application/foo; charset=utf-8'})
+self.assertEqual(response.headers.get('content-type'), 
'application/foo; charset=utf-8')
+self.assertEqual(response.body, unicode('ärger', 
'iso-8859-15').encode('utf-8'))
+
 def test_suite():
 suite = unittest.TestSuite()
 suite.addTest(unittest.makeSuite(HTTPResponseTests, 'test'))

___
Zope-Checkins maillist  -  Zope-Checkins@zope.org
http://mail.zope.org/mailman/listinfo/zope-checkins

[Zope-Checkins] SVN: Zope/branches/chrism-clockserver-merge/ Add clock server feature.

[Chris McDonough]

Log message for revision 40957:
  Add clock server feature.
  
  

Changed:
  U   Zope/branches/chrism-clockserver-merge/doc/CHANGES.txt
  A   Zope/branches/chrism-clockserver-merge/lib/python/ZServer/ClockServer.py
  U   Zope/branches/chrism-clockserver-merge/lib/python/ZServer/component.xml
  U   Zope/branches/chrism-clockserver-merge/lib/python/ZServer/datatypes.py
  A   
Zope/branches/chrism-clockserver-merge/lib/python/ZServer/tests/test_clockserver.py
  U   
Zope/branches/chrism-clockserver-merge/lib/python/ZServer/tests/test_config.py
  U   Zope/branches/chrism-clockserver-merge/skel/etc/zope.conf.in

-=-
Modified: Zope/branches/chrism-clockserver-merge/doc/CHANGES.txt
===
--- Zope/branches/chrism-clockserver-merge/doc/CHANGES.txt  2005-12-21 
15:12:00 UTC (rev 40956)
+++ Zope/branches/chrism-clockserver-merge/doc/CHANGES.txt  2005-12-21 
15:22:34 UTC (rev 40957)
@@ -26,6 +26,58 @@
 
 Features added
 
+  - Added a clock server servertype which allows users to
+configure methods that should be called periodically as if
+they were being called by a remote user agent on one of Zope's
+HTTP ports.  This is meant to replace wget+cron for some class
+of periodic callables.
+
+To use, create a clock-server directive section anywhere
+in your zope.conf file, like so:
+
+ clock-server
+method /do_stuff
+period 60
+user admin
+password 123
+host localhost
+ /clock-server
+
+Any number of clock-server sections may be defined within a
+single zope.conf.  Note that you must specify a
+username/password combination with the appropriate level of
+access to call the method you've defined.  You can omit the
+username and password if the method is anonymously callable.
+Obviously the password is stored in the clear in the config
+file, so you need to protect the config file with filesystem
+security if the Zope account is privileged and those who have
+filesystem access should not see the password.
+
+Descriptions of the values within the clock-server section
+follow::
+
+  method -- the traversal path (from the Zope root) to an
+  executable Zope method (Python Script, external method,
+  product method, etc).  The method must take no arguments or
+  must obtain its arguments from a query string.
+
+  period -- the number of seconds between each clock tick (and
+  thus each call to the above method).  The lowest number
+  providable here is typically 30 (this is the asyncore mainloop
+  timeout value).
+
+  user -- a zope username.
+
+  password -- the password for the zope username provided above.
+
+  host -- the hostname passed in via the Host: header in the
+  faux request.  Could be useful if you have virtual host rules
+  set up inside Zope itself.
+
+To make sure the clock is working, examine your Z2.log file.  It
+should show requests incoming via a Zope Clock Server
+useragent.
+
   - Added a 'conflict-error-log-level' directive to zope.conf, to set
 the level at which conflict errors (which are normally retried
 automatically) are logged. The default is 'info'.

Added: Zope/branches/chrism-clockserver-merge/lib/python/ZServer/ClockServer.py
===
--- Zope/branches/chrism-clockserver-merge/lib/python/ZServer/ClockServer.py
2005-12-21 15:12:00 UTC (rev 40956)
+++ Zope/branches/chrism-clockserver-merge/lib/python/ZServer/ClockServer.py
2005-12-21 15:22:34 UTC (rev 40957)
@@ -0,0 +1,161 @@
+##
+#
+# Copyright (c) 2005 Chris McDonough. All Rights Reserved.
+#
+# This software is subject to the provisions of the Zope Public License,
+# Version 2.1 (ZPL).  A copy of the ZPL should accompany this distribution.
+# THIS SOFTWARE IS PROVIDED AS IS AND ANY AND ALL EXPRESS OR IMPLIED
+# WARRANTIES ARE DISCLAIMED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
+# WARRANTIES OF TITLE, MERCHANTABILITY, AGAINST INFRINGEMENT, AND FITNESS
+# FOR A PARTICULAR PURPOSE
+#
+##
+
+ Zope clock server.  Generate a faux HTTP request on a regular basis
+by coopting the asyncore API. 
+
+import os
+import socket
+import time
+import StringIO
+import asyncore
+
+from ZServer.medusa.http_server import http_request
+from ZServer.medusa.default_handler import unquote
+from ZServer.PubCore import handle
+from ZServer.HTTPResponse import make_response
+from ZPublisher.HTTPRequest import HTTPRequest
+
+def timeslice(period, when=None, t=time.time):
+if when is None:
+when =  t()
+

[Zope-Checkins] SVN: Zope/branches/2.9/lib/python/Testing/ZopeTestCase/zopedoctest/ Content-Type header now contains a charset.

[Stefan H. Holek]

Log message for revision 40959:
  Content-Type header now contains a charset.
  

Changed:
  U   
Zope/branches/2.9/lib/python/Testing/ZopeTestCase/zopedoctest/FunctionalDocTest.txt
  U   
Zope/branches/2.9/lib/python/Testing/ZopeTestCase/zopedoctest/testFunctionalDocTest.py

-=-
Modified: 
Zope/branches/2.9/lib/python/Testing/ZopeTestCase/zopedoctest/FunctionalDocTest.txt
===
--- 
Zope/branches/2.9/lib/python/Testing/ZopeTestCase/zopedoctest/FunctionalDocTest.txt
 2005-12-21 15:33:11 UTC (rev 40958)
+++ 
Zope/branches/2.9/lib/python/Testing/ZopeTestCase/zopedoctest/FunctionalDocTest.txt
 2005-12-21 15:45:06 UTC (rev 40959)
@@ -82,7 +82,7 @@
   ... , handle_errors=False)
   HTTP/1.1 200 OK
   Content-Length: 5
-  Content-Type: text/plain
+  Content-Type: text/plain; charset=...
   BLANKLINE
   index
 
@@ -93,7 +93,7 @@
   ... , handle_errors=False)
   HTTP/1.1 200 OK
   Content-Length: 1
-  Content-Type: text/plain
+  Content-Type: text/plain; charset=...
   BLANKLINE
   1
 
@@ -104,7 +104,7 @@
   ... , handle_errors=False)
   HTTP/1.1 200 OK
   Content-Length: 1
-  Content-Type: text/plain
+  Content-Type: text/plain; charset=...
   BLANKLINE
   3
 
@@ -174,7 +174,7 @@
   ... , handle_errors=False)
   HTTP/1.1 200 OK
   Content-Length: 23
-  Content-Type: text/plain
+  Content-Type: text/plain; charset=...
   BLANKLINE
   foo: bar
   baz: oki doki

Modified: 
Zope/branches/2.9/lib/python/Testing/ZopeTestCase/zopedoctest/testFunctionalDocTest.py
===
--- 
Zope/branches/2.9/lib/python/Testing/ZopeTestCase/zopedoctest/testFunctionalDocTest.py
  2005-12-21 15:33:11 UTC (rev 40958)
+++ 
Zope/branches/2.9/lib/python/Testing/ZopeTestCase/zopedoctest/testFunctionalDocTest.py
  2005-12-21 15:45:06 UTC (rev 40959)
@@ -35,7 +35,7 @@
 ... )
 HTTP/1.1 200 OK
 Content-Length: 5
-Content-Type: text/plain
+Content-Type: text/plain; charset=...
 BLANKLINE
 index
 '''

___
Zope-Checkins maillist  -  Zope-Checkins@zope.org
http://mail.zope.org/mailman/listinfo/zope-checkins

[Zope-Checkins] SVN: Zope/branches/chrism-clockserver-merge/lib/python/ZServer/tests/test_c Fix test breakage caused by a nonuptodate test_config in initial branch.

[Chris McDonough]

Log message for revision 40961:
  Fix test breakage caused by a nonuptodate test_config in initial branch.
  

Changed:
  U   
Zope/branches/chrism-clockserver-merge/lib/python/ZServer/tests/test_clockserver.py
  U   
Zope/branches/chrism-clockserver-merge/lib/python/ZServer/tests/test_config.py

-=-
Modified: 
Zope/branches/chrism-clockserver-merge/lib/python/ZServer/tests/test_clockserver.py
===
--- 
Zope/branches/chrism-clockserver-merge/lib/python/ZServer/tests/test_clockserver.py
 2005-12-21 15:47:40 UTC (rev 40960)
+++ 
Zope/branches/chrism-clockserver-merge/lib/python/ZServer/tests/test_clockserver.py
 2005-12-21 16:02:43 UTC (rev 40961)
@@ -117,7 +117,7 @@
 self.assertEqual(handler.arg, [])
 time.sleep(1.1) # allow timeslice to switch
 self.assertEqual(server.readable(), False)
-self.assertEqual(handler.arg[0], 'Zope')
+self.assertEqual(handler.arg[0], 'Zope2')
 from ZServer.HTTPResponse import HTTPResponse
 from ZPublisher.HTTPRequest import HTTPRequest
 self.assert_(isinstance(handler.arg[1], HTTPRequest))

Modified: 
Zope/branches/chrism-clockserver-merge/lib/python/ZServer/tests/test_config.py
===
--- 
Zope/branches/chrism-clockserver-merge/lib/python/ZServer/tests/test_config.py  
2005-12-21 15:47:40 UTC (rev 40960)
+++ 
Zope/branches/chrism-clockserver-merge/lib/python/ZServer/tests/test_config.py  
2005-12-21 16:02:43 UTC (rev 40961)
@@ -243,7 +243,6 @@
 self.assertEqual(factory.user, 'chrism')
 self.assertEqual(factory.password, '123')
 self.assertEqual(factory.hostheader, 'www.example.com')
-self.check_prepare(factory)
 factory.create().close()
 
 

___
Zope-Checkins maillist  -  Zope-Checkins@zope.org
http://mail.zope.org/mailman/listinfo/zope-checkins

[Zope-Checkins] SVN: Zope/trunk/ HTTPResponse: for XML content the encoding specified within

[Andreas Jung]

Log message for revision 40965:
  HTTPResponse: for XML content the encoding specified within
  the XML preamble is adjusted to the real encoding of the content
  as specified through the 'charset' within the content-type
  property.
  

Changed:
  U   Zope/trunk/doc/CHANGES.txt
  U   Zope/trunk/lib/python/ZPublisher/HTTPResponse.py
  U   Zope/trunk/lib/python/ZPublisher/tests/testHTTPResponse.py

-=-
Modified: Zope/trunk/doc/CHANGES.txt
===
--- Zope/trunk/doc/CHANGES.txt  2005-12-21 17:33:31 UTC (rev 40964)
+++ Zope/trunk/doc/CHANGES.txt  2005-12-21 18:53:31 UTC (rev 40965)
@@ -176,6 +176,12 @@
 
 Bugs Fixed
 
+  - HTTPResponse: for XML content the encoding specified within
+the XML preamble is adjusted to the real encoding of the content
+as specified through the 'charset' within the content-type
+property.
+
+
   - Collector #1939: When running as a service, Zope could
 potentially collect too much log output filling the NT Event
 Log. When that happened, a 'print' during exception handling

Modified: Zope/trunk/lib/python/ZPublisher/HTTPResponse.py
===
--- Zope/trunk/lib/python/ZPublisher/HTTPResponse.py2005-12-21 17:33:31 UTC 
(rev 40964)
+++ Zope/trunk/lib/python/ZPublisher/HTTPResponse.py2005-12-21 18:53:31 UTC 
(rev 40965)
@@ -444,13 +444,26 @@
   r'charset=([-_0-9a-z]+' +
   r')(?:(?:\s*;)|\Z)',
   re.IGNORECASE)):
+
+def fix_xml_preamble(body, encoding):
+ fixes the encoding in the XML preamble according
+to the charset specified in the content-type header.
+
+
+if body.startswith('?xml'):
+pos_right = body.find('?')  # right end of the XML preamble
+body = ('?xml version=1.0 encoding=%s ?' % encoding) + 
body[pos_right+2:]
+return body
+
 # Encode the Unicode data as requested
 
 if self.headers.has_key('content-type'):
 match = charset_re.match(self.headers['content-type'])
 if match:
 encoding = match.group(1)
-return body.encode(encoding)
+body = body.encode(encoding)
+body = fix_xml_preamble(body, encoding)
+return body
 else:
 
 ct = self.headers['content-type']
@@ -458,7 +471,9 @@
 self.headers['content-type'] = '%s; charset=%s' % (ct, 
default_encoding)
 
 # Use the default character encoding
-return body.encode(default_encoding,'replace')
+body = body.encode(default_encoding,'replace')
+body = fix_xml_preamble(body, default_encoding)
+return body
 
 def setBase(self,base):
 Set the base URL for the returned document.

Modified: Zope/trunk/lib/python/ZPublisher/tests/testHTTPResponse.py
===
--- Zope/trunk/lib/python/ZPublisher/tests/testHTTPResponse.py  2005-12-21 
17:33:31 UTC (rev 40964)
+++ Zope/trunk/lib/python/ZPublisher/tests/testHTTPResponse.py  2005-12-21 
18:53:31 UTC (rev 40965)
@@ -98,6 +98,14 @@
 self.assertEqual(response.headers.get('content-type'), 
'application/foo; charset=utf-8')
 self.assertEqual(response.body, unicode('ärger', 
'iso-8859-15').encode('utf-8'))
 
+def test_XMLEncodingRecoding(self):
+xml = u'?xml version=1.0 encoding=iso-8859-15 
?\nfoobar//foo'
+response = self._makeOne(body=xml, headers={'content-type': 
'application/foo; charset=utf-8'})
+self.assertEqual('encoding=utf-8' in response.body, True)
+response = self._makeOne(body=xml, headers={'content-type': 
'application/foo; charset=iso-8859-15'})
+self.assertEqual('encoding=iso-8859-15' in response.body, True)
+
+
 def test_suite():
 suite = unittest.TestSuite()
 suite.addTest(unittest.makeSuite(HTTPResponseTests, 'test'))

___
Zope-Checkins maillist  -  Zope-Checkins@zope.org
http://mail.zope.org/mailman/listinfo/zope-checkins

[Zope-Checkins] SVN: Zope/trunk/lib/python/ZServer/ClockServer.py Fix breakage on Windows due to misuse of os.path (use posixpath instead).

[Chris McDonough]

Log message for revision 40966:
  Fix breakage on Windows due to misuse of os.path (use posixpath instead).
  

Changed:
  U   Zope/trunk/lib/python/ZServer/ClockServer.py

-=-
Modified: Zope/trunk/lib/python/ZServer/ClockServer.py
===
--- Zope/trunk/lib/python/ZServer/ClockServer.py2005-12-21 18:53:31 UTC 
(rev 40965)
+++ Zope/trunk/lib/python/ZServer/ClockServer.py2005-12-21 21:00:38 UTC 
(rev 40966)
@@ -14,6 +14,7 @@
  Zope clock server.  Generate a faux HTTP request on a regular basis
 by coopting the asyncore API. 
 
+import posixpath
 import os
 import socket
 import time
@@ -118,8 +119,8 @@
 # ZPublisher doesn't want the leading '?'
 query = query[1:]
 env['PATH_INFO']= '/' + path
-env['PATH_TRANSLATED']= os.path.normpath(
-os.path.join(os.getcwd(), env['PATH_INFO']))
+env['PATH_TRANSLATED']= posixpath.normpath(
+posixpath.join(os.getcwd(), env['PATH_INFO']))
 if query:
 env['QUERY_STRING'] = query
 env['channel.creation_time']=time.time()

___
Zope-Checkins maillist  -  Zope-Checkins@zope.org
http://mail.zope.org/mailman/listinfo/zope-checkins

[Zope-Checkins] SVN: Zope/branches/Zope-2_8-branch/lib/python/Testing/ZopeTestCase/testZODBCompat.py Added two more tests for transaction.abort().

[Stefan H. Holek]

Log message for revision 40967:
  Added two more tests for transaction.abort().
  

Changed:
  U   
Zope/branches/Zope-2_8-branch/lib/python/Testing/ZopeTestCase/testZODBCompat.py

-=-
Modified: 
Zope/branches/Zope-2_8-branch/lib/python/Testing/ZopeTestCase/testZODBCompat.py
===
--- 
Zope/branches/Zope-2_8-branch/lib/python/Testing/ZopeTestCase/testZODBCompat.py 
2005-12-21 21:00:38 UTC (rev 40966)
+++ 
Zope/branches/Zope-2_8-branch/lib/python/Testing/ZopeTestCase/testZODBCompat.py 
2005-12-21 21:09:27 UTC (rev 40967)
@@ -27,6 +27,7 @@
 
 import transaction
 
+from Acquisition import aq_base
 from AccessControl.Permissions import add_documents_images_and_files
 from AccessControl.Permissions import delete_objects
 import tempfile
@@ -350,7 +351,24 @@
 # This time the abort nukes the _v_foo attribute...
 self.failIf(hasattr(self.folder, '_v_foo'))
 
+def testTransactionAbortClassAttribute(self):
+self.folder.id = 'bar'
+self.failUnless(hasattr(aq_base(self.folder), 'id'))
+transaction.abort()
+# The id attribute is still present
+self.assertEqual(getattr(aq_base(self.folder), 'id', None), 'bar')
 
+def testSubTransactionAbortClassAttribute(self):
+self.folder.id = 'bar'
+self.failUnless(hasattr(aq_base(self.folder), 'id'))
+transaction.commit(1)
+transaction.abort()
+# The id attribute is still present but has been
+# reset to the class default
+self.failUnless(hasattr(aq_base(self.folder), 'id'))
+self.assertEqual(getattr(aq_base(self.folder), 'id', None), '')
+
+
 def test_suite():
 from unittest import TestSuite, makeSuite
 suite = TestSuite()

___
Zope-Checkins maillist  -  Zope-Checkins@zope.org
http://mail.zope.org/mailman/listinfo/zope-checkins

[Zope-Checkins] SVN: Zope/trunk/lib/python/zope/ update to latest Z3 trunk

[Andreas Jung]

Log message for revision 40971:
  update to latest Z3 trunk
  

Changed:
  _U  Zope/trunk/lib/python/zope/

-=-

Property changes on: Zope/trunk/lib/python/zope
___
Name: svn:externals
   - app  -r 40688 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/app
cachedescriptors -r 40688 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/cachedescriptors
component-r 40688 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/component
configuration-r 40688 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/configuration
documenttemplate -r 40688 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/documenttemplate
event-r 40688 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/event
exceptions   -r 40688 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/exceptions
hookable -r 40688 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/hookable
i18n -r 40688 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/i18n
i18nmessageid-r 40688 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/i18nmessageid
interface-r 40688 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/interface
modulealias  -r 40688 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/modulealias
pagetemplate -r 40688 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/pagetemplate
proxy-r 40688 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/proxy
publisher-r 40688 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/publisher
schema   -r 40688 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/schema
security -r 40688 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/security
server   -r 40688 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/server
structuredtext   -r 40688 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/structuredtext
tal  -r 40688 svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/tal
tales-r 40688 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/tales
testing  -r 40941 
svn://svn.zope.org/repos/main/zope.testing/trunk/src/zope/testing
thread   -r 40688 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/thread
deprecation  -r 40688 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/deprecation
dottedname   -r 40688 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/dottedname
formlib  -r 40688 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/formlib
index-r 40688 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/index
testbrowser  -r 40688 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/testbrowser

   + app  -r 40759 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/app
cachedescriptors -r 40759 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/cachedescriptors
component-r 40759 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/component
configuration-r 40759 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/configuration
documenttemplate -r 40759 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/documenttemplate
event-r 40759 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/event
exceptions   -r 40759 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/exceptions
hookable -r 40759 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/hookable
i18n -r 40759 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/i18n
i18nmessageid-r 40759 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/i18nmessageid
interface-r 40759 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/interface
modulealias  -r 40759 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/modulealias
pagetemplate -r 40759 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/pagetemplate
proxy-r 40759 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/proxy
publisher-r 40759 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/publisher
schema   -r 40759 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/schema
security -r 40759 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/security
server   -r 40759 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/server
structuredtext   -r 40759 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/structuredtext
tal  -r 40759 svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/tal
tales-r 40759 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/tales
testing  -r 40941 
svn://svn.zope.org/repos/main/zope.testing/trunk/src/zope/testing
thread   -r 40759 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/thread
deprecation  -r 40759 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/deprecation
dottedname   -r 40759 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/dottedname
formlib  -r 40759 

[Zope-Checkins] SVN: Zope/trunk/lib/python/zope/ updated to latest Z3 trunk

[Andreas Jung]

Log message for revision 40972:
  updated to latest Z3 trunk
  

Changed:
  _U  Zope/trunk/lib/python/zope/

-=-

Property changes on: Zope/trunk/lib/python/zope
___
Name: svn:externals
   - app  -r 40759 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/app
cachedescriptors -r 40759 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/cachedescriptors
component-r 40759 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/component
configuration-r 40759 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/configuration
documenttemplate -r 40759 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/documenttemplate
event-r 40759 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/event
exceptions   -r 40759 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/exceptions
hookable -r 40759 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/hookable
i18n -r 40759 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/i18n
i18nmessageid-r 40759 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/i18nmessageid
interface-r 40759 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/interface
modulealias  -r 40759 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/modulealias
pagetemplate -r 40759 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/pagetemplate
proxy-r 40759 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/proxy
publisher-r 40759 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/publisher
schema   -r 40759 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/schema
security -r 40759 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/security
server   -r 40759 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/server
structuredtext   -r 40759 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/structuredtext
tal  -r 40759 svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/tal
tales-r 40759 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/tales
testing  -r 40941 
svn://svn.zope.org/repos/main/zope.testing/trunk/src/zope/testing
thread   -r 40759 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/thread
deprecation  -r 40759 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/deprecation
dottedname   -r 40759 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/dottedname
formlib  -r 40759 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/formlib
index-r 40759 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/index
testbrowser  -r 40759 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/testbrowser

   + app  -r 40971 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/app
cachedescriptors -r 40971 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/cachedescriptors
component-r 40971 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/component
configuration-r 40971 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/configuration
documenttemplate -r 40971 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/documenttemplate
event-r 40971 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/event
exceptions   -r 40971 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/exceptions
hookable -r 40971 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/hookable
i18n -r 40971 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/i18n
i18nmessageid-r 40971 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/i18nmessageid
interface-r 40971 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/interface
modulealias  -r 40971 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/modulealias
pagetemplate -r 40971 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/pagetemplate
proxy-r 40971 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/proxy
publisher-r 40971 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/publisher
schema   -r 40971 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/schema
security -r 40971 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/security
server   -r 40971 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/server
structuredtext   -r 40971 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/structuredtext
tal  -r 40971 svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/tal
tales-r 40971 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/tales
testing  -r 40941 
svn://svn.zope.org/repos/main/zope.testing/trunk/src/zope/testing
thread   -r 40971 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/thread
deprecation  -r 40971 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/deprecation
dottedname   -r 40971 
svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/dottedname
formlib  -r 40971 

Re: [Zope-dev] [RfC] Removal of old stuff in Zope 2.10

[Martijn Faassen]

Andreas Jung wrote:


- HelpSys - from a programmers view pretty much useless and not very
  helpful. I consider to replace it with something more useful (not sure
  we can re-use apidoc from Zope 3 in some way, perhaps the inclusion
  of Dieter's Docfinder might be more useful for programmers)


Formulator's using this and I think it might be used by some people. I'm 
okay with trying to switch Formulator on to something like apidoc though.


Regards,

Martijn
___
Zope-Dev maillist  -  Zope-Dev@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 )

[Zope-dev] buildbot failure in Zope branches 2.9 2.4 Windows 2000 zc-bbwin

[buildbot]

The Buildbot has detected a failed build of Zope branches 2.9 2.4 Windows 2000 
zc-bbwin.

Buildbot URL: http://buildbot.zope.org/

Build Reason: changes
Build Source Stamp: 2390
Blamelist: andreasjung,anguenot,efge,sidnei

BUILD FAILED: failed test

sincerely,
 -The Buildbot

___
Zope-Dev maillist  -  Zope-Dev@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 )

[Zope-dev] Zope tests: 7 OK, 1 Failed

[Zope tests summarizer]

Summary of messages to the zope-tests list.
Period Tue Dec 20 12:01:02 2005 UTC to Wed Dec 21 12:01:02 2005 UTC.
There were 8 messages: 8 from Zope Unit Tests.


Test failures
-

Subject: FAILED (errors=1) : Zope-2_7-branch Python-2.4.2 :
Linux
From: Zope Unit Tests
Date: Tue Dec 20 21:17:40 EST 2005
URL: http://mail.zope.org/pipermail/zope-tests/2005-December/003813.html


Tests passed OK
---

Subject: OK : Zope-2_6-branch Python-2.1.3 : Linux
From: Zope Unit Tests
Date: Tue Dec 20 21:13:10 EST 2005
URL: http://mail.zope.org/pipermail/zope-tests/2005-December/003810.html

Subject: OK : Zope-2_6-branch Python-2.3.5 : Linux
From: Zope Unit Tests
Date: Tue Dec 20 21:14:40 EST 2005
URL: http://mail.zope.org/pipermail/zope-tests/2005-December/003811.html

Subject: OK : Zope-2_7-branch Python-2.3.5 : Linux
From: Zope Unit Tests
Date: Tue Dec 20 21:16:10 EST 2005
URL: http://mail.zope.org/pipermail/zope-tests/2005-December/003812.html

Subject: OK : Zope-2_8-branch Python-2.3.5 : Linux
From: Zope Unit Tests
Date: Tue Dec 20 21:19:10 EST 2005
URL: http://mail.zope.org/pipermail/zope-tests/2005-December/003814.html

Subject: OK : Zope-2_8-branch Python-2.4.2 : Linux
From: Zope Unit Tests
Date: Tue Dec 20 21:20:41 EST 2005
URL: http://mail.zope.org/pipermail/zope-tests/2005-December/003815.html

Subject: OK : Zope-2_9-branch Python-2.4.2 : Linux
From: Zope Unit Tests
Date: Tue Dec 20 21:22:11 EST 2005
URL: http://mail.zope.org/pipermail/zope-tests/2005-December/003816.html

Subject: OK : Zope-trunk Python-2.4.2 : Linux
From: Zope Unit Tests
Date: Tue Dec 20 21:23:41 EST 2005
URL: http://mail.zope.org/pipermail/zope-tests/2005-December/003817.html

___
Zope-Dev maillist  -  Zope-Dev@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 )

[Zope-dev] buildbot failure in Zope trunk 2.4 Windows 2000 zc-bbwin

[buildbot]

The Buildbot has detected a failed build of Zope trunk 2.4 Windows 2000 
zc-bbwin.

Buildbot URL: http://buildbot.zope.org/

Build Reason: changes
Build Source Stamp: 2391
Blamelist: andreasjung,anguenot,efge,sidnei

BUILD FAILED: failed test

sincerely,
 -The Buildbot

___
Zope-Dev maillist  -  Zope-Dev@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 )

[Zope-dev] buildbot failure in Zope trunk 2.4 Windows 2000 zc-bbwin

[buildbot]

The Buildbot has detected a failed build of Zope trunk 2.4 Windows 2000 
zc-bbwin.

Buildbot URL: http://buildbot.zope.org/

Build Reason: changes
Build Source Stamp: 2397
Blamelist: efge,sidnei

BUILD FAILED: failed test

sincerely,
 -The Buildbot

___
Zope-Dev maillist  -  Zope-Dev@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 )

[Zope-dev] buildbot failure in Zope branches 2.9 2.4 Windows 2000 zc-bbwin

[buildbot]

The Buildbot has detected a failed build of Zope branches 2.9 2.4 Windows 2000 
zc-bbwin.

Buildbot URL: http://buildbot.zope.org/

Build Reason: changes
Build Source Stamp: 2398
Blamelist: efge,sidnei

BUILD FAILED: failed test

sincerely,
 -The Buildbot

___
Zope-Dev maillist  -  Zope-Dev@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 )

[Zope-dev] Re: buildbot failure in Zope branches 2.9 2.4 Windows 2000 zc-bbwin

[Florent Guillaume]

[EMAIL PROTECTED] wrote:

The Buildbot has detected a failed build of Zope branches 2.9 2.4 Windows 2000 
zc-bbwin.

Buildbot URL: http://buildbot.zope.org/

Build Reason: changes
Build Source Stamp: 2398
Blamelist: efge,sidnei

BUILD FAILED: failed test


FYI test output is:


C:\WINDOWS\system32\cmd.exe /c c:\python24\python.exe test.py -v -m 
!^^(ZEO|zope[.]app[.]) --all
 in dir C:\buildbot\.org\zc-bbwin--Windows 
2000--Zope---branches---2.9--2.4\build (timeout 1200 secs)
 argv: ['C:\\WINDOWS\\system32\\cmd.exe', '/c', 'c:\\python24\\python.exe 
test.py -v -m !^^(ZEO|zope[.]app[.]) --all']
 environment: {'TMP': 'C:\\DOCUME~1\\buildbot\\LOCALS~1\\Temp', 
'COMPUTERNAME': 'BBWIN', 'LIB': 'C:\\Program Files\\Microsoft Visual Studio 
.NET 2003\\SDK\\v1.1\\Lib\\', 'USERDOMAIN': 'BBWIN', 'PYTHON': 
'c:\\python24\\python.exe', 'COMMONPROGRAMFILES': 'C:\\Program Files\\Common 
Files', 'PROCESSOR_IDENTIFIER': 'x86 Family 15 Model 4 Stepping 1, 
GenuineIntel', 'PROGRAMFILES': 'C:\\Program Files', 'PROCESSOR_REVISION': 
'0401', 'SYSTEMROOT': 'C:\\WINDOWS', 'PATH': 
'C:\\WINDOWS\\system32;C:\\WINDOWS;C:\\WINDOWS\\System32\\Wbem;c:\\utils;C:\\Program 
Files\\Subversion\\bin', 'VIM': 'C:\\Program Files\\Vim', 'TEMP': 
'C:\\DOCUME~1\\buildbot\\LOCALS~1\\Temp', 'PROCESSOR_ARCHITECTURE': 'x86', 
'VS71COMNTOOLS': 'C:\\Program Files\\Microsoft Visual Studio .NET 
2003\\Common7\\Tools\\', 'APR_ICONV_PATH': 'C:\\Program 
Files\\Subversion\\iconv', 'ALLUSERSPROFILE': 'C:\\Documents and 
Settings\\All Users', 'INSTANCE_HOME': 
'C:\\buildbot\\.com\\bbwin--Windows--FIPS-1---trunk--2.4\\build\\instance', 
'SESSIONNAME': 'Console', 'HOMEPATH': '\\Documents and Settings\\buildbot', 
'USERNAME': 'buildbot', 'LOGONSERVER': 'BBWIN', 'PROMPT': '$P$G', 
'COMSPEC': 'C:\\WINDOWS\\system32\\cmd.exe', 'PATHEXT': 
'.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH', 'INCLUDE': 'C:\\Program 
Files\\Microsoft Visual Studio .NET 2003\\SDK\\v1.1\\include\\', 
'FP_NO_HOST_CHECK': 'NO', 'WINDIR': 'C:\\WINDOWS', 'HOMEDRIVE': 'C:', 
'APPDATA': 'C:\\Documents and Settings\\buildbot\\Application Data', 
'SYSTEMDRIVE': 'C:', 'NUMBER_OF_PROCESSORS': '1', 'SVN_SSH': 
'c:/putty/plink.exe', 'PROCESSOR_LEVEL': '15', 'OS': 'Windows_NT', 
'USERPROFILE': 'C:\\Documents and Settings\\buildbot'}

'zope[.]app[.])' is not recognized as an internal or external command,
operable program or batch file.
program finished with exit code 255

Florent

--
Florent Guillaume, Nuxeo (Paris, France)   CTO, Director of RD
+33 1 40 33 71 59   http://nuxeo.com   [EMAIL PROTECTED]
___
Zope-Dev maillist  -  Zope-Dev@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 )

[Zope-dev] buildbot failure in Zope branches 2.9 2.4 Windows 2000 zc-bbwin

[buildbot]

The Buildbot has detected a failed build of Zope branches 2.9 2.4 Windows 2000 
zc-bbwin.

Buildbot URL: http://buildbot.zope.org/

Build Reason: The web-page 'force build' button was pressed by '': 

Build Source Stamp: None
Blamelist: 

BUILD FAILED: failed failed slave lost

sincerely,
 -The Buildbot

___
Zope-Dev maillist  -  Zope-Dev@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 )

[Zope-dev] buildbot failure in Zope trunk 2.4 Windows 2000 zc-bbwin

[buildbot]

The Buildbot has detected a failed build of Zope trunk 2.4 Windows 2000 
zc-bbwin.

Buildbot URL: http://buildbot.zope.org/

Build Reason: changes
Build Source Stamp: 2402
Blamelist: andreasjung

BUILD FAILED: failed failed slave lost

sincerely,
 -The Buildbot

___
Zope-Dev maillist  -  Zope-Dev@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 )

Re: [Zope-dev] Re: svn.zope.org borked

[Jim Fulton]

I'm going to go ahead with this update in hopes of resolving some
windows client problems that may be confounding our efforts to
run windows tests with buildbot.

Jim

Jens Vagelpohl wrote:


On 19 Dec 2005, at 22:08, Jim Fulton wrote:


Sounds good.  I'll announce that the repo will be down for maintenance
on the 25th,




Just FYI, during a dry run this morning I hit an obvious snag: The  
subversion packages on svn.zope.org are so ancient that they cannot  
create FSFS backends. What I was able to test so far is dumping: It  
takes just 10 minutes and creates a file 1.1GB in size, so that's good.


I had a look at the packages on the box and luckily the (rather  
obscure) source they are from does supply newer ones:


http://summersoft.fay.ar.us/pub/subversion/latest/redhat-9.0/bin/

 From eyeballing the RPM requirements and then doing a dry-run the  
packages that will need updating are...


- swig (1.3.19-1.1 to 1.3.19-3)
- subversion (1.0.6-1 to 1.2.3-1)
- subversion-tools (1.0.6-1 to 1.2.3-1)
- subversion-python (1.0.6-1 to 1.2.3-1)

This additional packages needs to be installed for svn-tools:

- subversion-perl (1.2.3-1)

Since I cannot do any test right now for loading the dumpfile into a  
FSFS-based repository I suggest doing this package upgrade  beforehand. 
It only takes a few minutes. I cannot make any guarantees  that nothing 
will break, however. The only major upgrade to a running  SVN setup that 
I have done was 1.1 to 1.2.1 and that was perfectly fine.


How should I proceed?

jens




--
Jim Fulton   mailto:[EMAIL PROTECTED]   Python Powered!
CTO  (540) 361-1714http://www.python.org
Zope Corporation http://www.zope.com   http://www.zope.org
___
Zope-Dev maillist  -  Zope-Dev@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 )

Re: [Zope-dev] Re: svn.zope.org borked

[Jens Vagelpohl]

Does that mean you're doing it? All necessary RPMs are on the box at / 
root/svnupgrade/. Otherwise I can do it tomorrow morning (about 5 AM  
EST)


jens


On 21 Dec 2005, at 16:08, Jim Fulton wrote:


I'm going to go ahead with this update in hopes of resolving some
windows client problems that may be confounding our efforts to
run windows tests with buildbot.

Jim

Jens Vagelpohl wrote:

On 19 Dec 2005, at 22:08, Jim Fulton wrote:
Sounds good.  I'll announce that the repo will be down for  
maintenance

on the 25th,
Just FYI, during a dry run this morning I hit an obvious snag:  
The  subversion packages on svn.zope.org are so ancient that they  
cannot  create FSFS backends. What I was able to test so far is  
dumping: It  takes just 10 minutes and creates a file 1.1GB in  
size, so that's good.
I had a look at the packages on the box and luckily the (rather   
obscure) source they are from does supply newer ones:

http://summersoft.fay.ar.us/pub/subversion/latest/redhat-9.0/bin/
 From eyeballing the RPM requirements and then doing a dry-run  
the  packages that will need updating are...

- swig (1.3.19-1.1 to 1.3.19-3)
- subversion (1.0.6-1 to 1.2.3-1)
- subversion-tools (1.0.6-1 to 1.2.3-1)
- subversion-python (1.0.6-1 to 1.2.3-1)
This additional packages needs to be installed for svn-tools:
- subversion-perl (1.2.3-1)
Since I cannot do any test right now for loading the dumpfile into  
a  FSFS-based repository I suggest doing this package upgrade   
beforehand. It only takes a few minutes. I cannot make any  
guarantees  that nothing will break, however. The only major  
upgrade to a running  SVN setup that I have done was 1.1 to 1.2.1  
and that was perfectly fine.

How should I proceed?
jens



--
Jim Fulton   mailto:[EMAIL PROTECTED]   Python Powered!
CTO  (540) 361-1714http://www.python.org
Zope Corporation http://www.zope.com   http://www.zope.org


___
Zope-Dev maillist  -  Zope-Dev@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 )

[Zope-dev] Re: [RfC] Removal of old stuff in Zope 2.10

[Max M]

Andreas Jung wrote:

Hi,



- Gadfly(DA) - do we really need this? We discussed this already. In my
  opinion the purpose of Gadfly is only educational but nothing that one
  really needs or uses for production. It could be removed and made
  available for download on zope.org.



-1

From time to time I teach classes on Zope. Often to people with an sql 
legacy. Most companies don't have a computer lab with similar machines, 
so often the educational software must be installed on the participants 
own machine. Which can be of any platform.


Using Gadfly as an educational tool is *very* practical. Eg. they can 
install Zope, and begin using sql at once.


Having to install postgres etc. just to teach about database connections 
etc. would be really impractical.



If there is another practical way to do it, that would be fine too. I 
don't know about sqllite. But if it's more difficulte than dropping a 
package into a directory it would be bad.


--

hilsen/regards Max M, Denmark

http://www.mxm.dk/
IT's Mad Science

___
Zope-Dev maillist  -  Zope-Dev@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 )

Re: [Zope-dev] Re: svn.zope.org borked

[Jim Fulton]

Jim Fulton wrote:

I'm going to go ahead with this update in hopes of resolving some
windows client problems that may be confounding our efforts to
run windows tests with buildbot.


Done

Jim

--
Jim Fulton   mailto:[EMAIL PROTECTED]   Python Powered!
CTO  (540) 361-1714http://www.python.org
Zope Corporation http://www.zope.com   http://www.zope.org
___
Zope-Dev maillist  -  Zope-Dev@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 )

Re: [Zope-dev] Re: svn.zope.org borked

[Jim Fulton]

Jens Vagelpohl wrote:
Does that mean you're doing it? All necessary RPMs are on the box at / 
root/svnupgrade/. Otherwise I can do it tomorrow morning (about 5 AM  EST)


Yes, already done. They are also available in my home directory. :)

Jim

--
Jim Fulton   mailto:[EMAIL PROTECTED]   Python Powered!
CTO  (540) 361-1714http://www.python.org
Zope Corporation http://www.zope.com   http://www.zope.org
___
Zope-Dev maillist  -  Zope-Dev@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 )

Re: [Zope-dev] Re: svn.zope.org borked

[Jens Vagelpohl]

On 21 Dec 2005, at 16:12, Jim Fulton wrote:


Jim Fulton wrote:

I'm going to go ahead with this update in hopes of resolving some
windows client problems that may be confounding our efforts to
run windows tests with buildbot.


Done


Great. I can see http://svn.zope.org works just fine.

With this upgrade in place I will do a new dry-run for the FSFS  
backend migration tomorrow morning.


jens

___
Zope-Dev maillist  -  Zope-Dev@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 )

[Zope-dev] buildbot failure in Zope trunk 2.4 Linux zc-buildbot

[buildbot]

The Buildbot has detected a failed build of Zope trunk 2.4 Linux zc-buildbot.

Buildbot URL: http://buildbot.zope.org/

Build Reason: changes
Build Source Stamp: 2409
Blamelist: chrism

BUILD FAILED: failed test

sincerely,
 -The Buildbot

___
Zope-Dev maillist  -  Zope-Dev@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 )

[Zope-dev] buildbot failure in Zope branches 2.9 2.4 Windows 2000 zc-bbwin

[buildbot]

The Buildbot has detected a failed build of Zope branches 2.9 2.4 Windows 2000 
zc-bbwin.

Buildbot URL: http://buildbot.zope.org/

Build Reason: The web-page 'force build' button was pressed by 'tim': try this 
bbwin build by itself

Build Source Stamp: None
Blamelist: 

BUILD FAILED: failed test

sincerely,
 -The Buildbot

___
Zope-Dev maillist  -  Zope-Dev@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 )

Re: [Zope-dev] Re: [RfC] Removal of old stuff in Zope 2.10

[Andreas Jung]

--On 21. Dezember 2005 17:10:19 +0100 Max M [EMAIL PROTECTED] wrote:


If there is another practical way to do it, that would be fine too. I
don't know about sqllite. But if it's more difficulte than dropping a
package into a directory it would be bad.




I mentioned to make it available as download. So you can install it when 
needed.


-aj


pgp8ItatpYMAz.pgp
Description: PGP signature
___
Zope-Dev maillist  -  Zope-Dev@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 )

[Zope-dev] buildbot failure in Zope trunk 2.4 Windows 2000 zc-bbwin

[buildbot]

The Buildbot has detected a failed build of Zope trunk 2.4 Windows 2000 
zc-bbwin.

Buildbot URL: http://buildbot.zope.org/

Build Reason: changes
Build Source Stamp: 2411
Blamelist: chrism

BUILD FAILED: failed test

sincerely,
 -The Buildbot

___
Zope-Dev maillist  -  Zope-Dev@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 )

Re: [Zope-dev] zope-2.9 r40780 make install doesn't finish, files missing from bin

[Martijn Faassen]

Jens Vagelpohl wrote:


On 20 Dec 2005, at 08:51, Stefan H. Holek wrote:


On 18. Dez 2005, at 17:58, Tim Peters wrote:


Nobody should be installing from a checkout to begin with, right?


Ok, so that's probably where we disagree then ;-)

I almost exclusively work with checkouts, and I would think many  
developers (as opposed to users) do. Is there really no way to  
allow make install to work from a sandbox?


I strongly disagree as well. I believe it is normal practice to grab  a 
tag or branch tip from subversion and install that. Why would I  ever 
grab some tarball when I'm at the command line already and use  svn for 
everything else, anyway? 


I'm not happy about this change either -- I just ran into it. I did the 
'configure; make; make install' dance, and suddenly I run into an error.
I like working with release tarballs but I don't like the experience to 
be different when I do a checkout. The least I expect is to run into an 
error message that doesn't tell me anything.


Regards,

Martijn
___
Zope-Dev maillist  -  Zope-Dev@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 )

Re: [Zope-dev] zope-2.9 r40780 make install doesn't finish, files missing from bin

[Martijn Faassen]

Andreas Jung wrote:

I agree. I am also not happy with that. Unfortunately I have currently 
no clue how to solve this issue (no idea about zpkg). WHat you can do is 
the following:


- copy the checkout to the location where your software home should be

- run configure; make inplace; make instance


Doesn't work for me; I don't have a bin/mkzopeinstance after this 
procedure so I still cannot create instances. Sigh.


Regards,

Martijn
___
Zope-Dev maillist  -  Zope-Dev@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 )

Re: [Zope-dev] zope-2.9 r40780 make install doesn't finish, files missing from bin

[Martijn Faassen]

Jeff Kowalczyk wrote:

I didn't receive any feedback on zope-general, but it could just be a
problem with my environment that fails silently. Can anyone confirm that
this isn't pilot error before I file a bug? Thanks.


From the thread, it's not a pilot error, so could you please file a bug 
if you haven't already?


I at least consider commands that simply fail to work in development 
checkouts with obscure errors as a bug.  I ran into this independently, 
and found this thread. If I had come by a few weeks later, I would 
likely not have found this thread, and I'd have asked the question 
again. If it at least said hey, this doesn't work, try this instead 
when you go 'make install', it'd be at least be something, though 
ideally any command that works in a release should also work in a 
development checkout.


I understand that the reason for this is zpkg. It's not the first time 
that zpkg slams me right into the head for various reasons. Going into 
the wider story of packaging philosophy, I suspect there are arguments 
to be made in favor of making the difference between the repository and 
the distribution small. A distribution could be *smaller* than a 
repository, i.e. a profile of what's in the repository, but it'd be nice 
if structurally what's actually included in a distribution was the same 
as much as possible as what's in the repository.


Regards,

Martijn
___
Zope-Dev maillist  -  Zope-Dev@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 )

Re: [Zope-dev] zope-2.9 r40780 make install doesn't finish, files missing from bin

[Jim Fulton]

Martijn Faassen wrote:

Jens Vagelpohl wrote:



On 20 Dec 2005, at 08:51, Stefan H. Holek wrote:


On 18. Dez 2005, at 17:58, Tim Peters wrote:


Nobody should be installing from a checkout to begin with, right?



Ok, so that's probably where we disagree then ;-)

I almost exclusively work with checkouts, and I would think many  
developers (as opposed to users) do. Is there really no way to  
allow make install to work from a sandbox?



I strongly disagree as well. I believe it is normal practice to grab  
a tag or branch tip from subversion and install that. Why would I  
ever grab some tarball when I'm at the command line already and use  
svn for everything else, anyway? 



I'm not happy about this change either -- I just ran into it. I did the 
'configure; make; make install' dance, and suddenly I run into an error.
I like working with release tarballs but I don't like the experience to 
be different when I do a checkout. The least I expect is to run into an 
error message that doesn't tell me anything.


I'll note, FWIW, that we don't do installs from Zope 3 checkouts.
I think it's worth asking whether this is an important requirement.
If it is, then we should make it work.  Question is, is it worth
delaying the release?  I don't know.

If we did stay with the current situation, we'd need to cleanup the
documentation so that a developer can easily reminder herself
what she can do and how to do it.

Jim

--
Jim Fulton   mailto:[EMAIL PROTECTED]   Python Powered!
CTO  (540) 361-1714http://www.python.org
Zope Corporation http://www.zope.com   http://www.zope.org
___
Zope-Dev maillist  -  Zope-Dev@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 )

Re: [Zope-dev] zope-2.9 r40780 make install doesn't finish, files missing from bin

[Andrew Sawyers]

On Wed, 2005-12-21 at 13:47 -0500, Jim Fulton wrote:

 
 I'll note, FWIW, that we don't do installs from Zope 3 checkouts.
 I think it's worth asking whether this is an important requirement.
 If it is, then we should make it work.  Question is, is it worth
 delaying the release?  I don't know.
I think it's an important requirement; many of us have done this dance
for years.  The reason I'd suspect this got done by Chris M was to ease
our pains we'd had to work around over time and make it easier for
people coming into the Zope Community - or their support staff (i.e.
Admins)  

I can't answer the last question, but it seems to apparent that it's
important and expected behavior by lots of people in the community.  

 
 If we did stay with the current situation, we'd need to cleanup the
 documentation so that a developer can easily reminder herself
 what she can do and how to do it.
If it's indeed *easy* and clear, that should be ok.  It just needs to
work sensibly  :)  So many of us are used to the ./configure; make; make
install dance.
 
 Jim
 

Andrew

___
Zope-Dev maillist  -  Zope-Dev@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 )

Re: [Zope-dev] zope-2.9 r40780 make install doesn't finish, files missing from bin

[Jim Fulton]

Andrew Sawyers wrote:

On Wed, 2005-12-21 at 13:47 -0500, Jim Fulton wrote:



I'll note, FWIW, that we don't do installs from Zope 3 checkouts.
I think it's worth asking whether this is an important requirement.
If it is, then we should make it work.  Question is, is it worth
delaying the release?  I don't know.


I think it's an important requirement; many of us have done this dance
for years.  The reason I'd suspect this got done by Chris M was to ease
our pains we'd had to work around over time and make it easier for
people coming into the Zope Community - or their support staff (i.e.
Admins)  


But those people use releases, not checkouts AFAIK.

...


If we did stay with the current situation, we'd need to cleanup the
documentation so that a developer can easily reminder herself
what she can do and how to do it.


If it's indeed *easy* and clear, that should be ok.  It just needs to
work sensibly  :)  So many of us are used to the ./configure; make; make
install dance.


I'll note that, as a developer, I have never done this and probably
never would want to do this.

The only use case for this is a deployer of Zope that wants to install an
unreleased revision of Zope.  If this use case is driving this, a better
solution might be to build automatic snapshot releases.

Jim

--
Jim Fulton   mailto:[EMAIL PROTECTED]   Python Powered!
CTO  (540) 361-1714http://www.python.org
Zope Corporation http://www.zope.com   http://www.zope.org
___
Zope-Dev maillist  -  Zope-Dev@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 )

[Zope-dev] What use cases are driving make install from a checkout?

[Jim Fulton]

I'd like to step back and see if we can agree on what is driving the desire
for make install.  I'll note that one reason is that it worked this way
before, but I don't think that that is a good enough reason to delay the
release.

I'll note one use case:

- A Zope deployer wants to deploy an unreleased version of Zope
  because they need some feature or bug fix that hasn't been
  released yet.

Can anyone think of other use cases?

Jim

--
Jim Fulton   mailto:[EMAIL PROTECTED]   Python Powered!
CTO  (540) 361-1714http://www.python.org
Zope Corporation http://www.zope.com   http://www.zope.org
___
Zope-Dev maillist  -  Zope-Dev@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 )

Re: [Zope-dev] Re: buildbot failure in Zope branches 2.9 2.4 Windows 2000 zc-bbwin

[Tim Peters]

[Florent Guillaume]
 FYI test output is:
 ...
 'zope[.]app[.])' is not recognized as an internal or external command,
 operable program or batch file.
 program finished with exit code 255

That was due to an ill-formed command line, which Jim repaired this
morning.  Zope trunk and Zope 2.9 branch are still failing on Windows,
though, with different symptoms now:


Failure in test test_checkPermission_proxy_role_scope
(AccessControl.tests.testZopeSecurityPolicy.C_ZSPTests)
Traceback (most recent call last):
  File c:\python24\lib\unittest.py, line 260, in run
testMethod()
  File C:\buildbot\.org\zc-bbwin--Windows
2000--Zope---trunk--2.4\build\lib\python\AccessControl\tests\testZopeSecurityPolicy.py,
line 326, in test_checkPermission_proxy_role_scope
self.failUnless(self.policy.checkPermission('Kill', r_subitem, context))
  File c:\python24\lib\unittest.py, line 309, in failUnless
if not expr: raise self.failureException, msg
AssertionError

.

Failure in test test_checkPermission_proxy_roles_limit_access
(AccessControl.tests.testZopeSecurityPolicy.C_ZSPTests)
Traceback (most recent call last):
  File c:\python24\lib\unittest.py, line 260, in run
testMethod()
  File C:\buildbot\.org\zc-bbwin--Windows
2000--Zope---trunk--2.4\build\lib\python\AccessControl\tests\testZopeSecurityPolicy.py,
line 302, in test_checkPermission_proxy_roles_limit_access
self.failIf(self.policy.checkPermission('Foo', r_item, context))
  File c:\python24\lib\unittest.py, line 305, in failIf
if expr: raise self.failureException, msg
AssertionError

.

Failure in test test_checkPermission_respects_proxy_roles
(AccessControl.tests.testZopeSecurityPolicy.C_ZSPTests)
Traceback (most recent call last):
  File c:\python24\lib\unittest.py, line 260, in run
testMethod()
  File C:\buildbot\.org\zc-bbwin--Windows
2000--Zope---trunk--2.4\build\lib\python\AccessControl\tests\testZopeSecurityPolicy.py,
line 291, in test_checkPermission_respects_proxy_roles
self.failUnless(self.policy.checkPermission('View', r_item, context))
  File c:\python24\lib\unittest.py, line 309, in failUnless
if not expr: raise self.failureException, msg
AssertionError


I don't have time to look at it.  Since the Windows buildbot slave
`bbwin` doesn't have a C compiler, I suppose it's possible that the
old, canned .pyd files it uses are out of synch with the current C
code.
___
Zope-Dev maillist  -  Zope-Dev@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 )

[Zope-dev] buildbot failure in Zope trunk 2.4 Windows 2000 zc-bbwin

[buildbot]

The Buildbot has detected a failed build of Zope trunk 2.4 Windows 2000 
zc-bbwin.

Buildbot URL: http://buildbot.zope.org/

Build Reason: changes
Build Source Stamp: 2412
Blamelist: andreasjung

BUILD FAILED: failed test

sincerely,
 -The Buildbot

___
Zope-Dev maillist  -  Zope-Dev@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 )

Re: [Zope-dev] zope-2.9 r40780 make install doesn't finish, files missing from bin

[Jens Vagelpohl]

On 21 Dec 2005, at 18:47, Jim Fulton wrote:

I'll note, FWIW, that we don't do installs from Zope 3 checkouts.
I think it's worth asking whether this is an important requirement.
If it is, then we should make it work.  Question is, is it worth
delaying the release?  I don't know.


IMHO it is an important requirement. We're inviting a hailstorm of  
questions and annoyed users by breaking this well-known routine for  
checkouts.


I really think there is not a single good reason for having a  
different experience for checkouts vs tarballs. It would even lead to  
major annoyance where I work right now, just to give a real life  
example. For us, building out a development sandbox is the same  
process as building out a production instance, and for development  
buildouts we routinely want to just substitute checkous from a  
different tag/branch of Zope.


jens

___
Zope-Dev maillist  -  Zope-Dev@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 )

Re: [Zope-dev] zope-2.9 r40780 make install doesn't finish, files missing from bin

[Andreas Jung]

--On 21. Dezember 2005 19:35:35 + Jens Vagelpohl [EMAIL PROTECTED] 
wrote:

I really think there is not a single good reason for having a  different
experience for checkouts vs tarballs. It would even lead to  major
annoyance where I work right now, just to give a real life  example. For
us, building out a development sandbox is the same  process as building
out a production instance, and for development  buildouts we routinely
want to just substitute checkous from a  different tag/branch of Zope.



Who has the knowledge and time to fix this?

-aj


pgpXxv3ntvSUU.pgp
Description: PGP signature
___
Zope-Dev maillist  -  Zope-Dev@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 )

[Zope-dev] buildbot failure in Zope trunk 2.4 Windows 2000 zc-bbwin

[buildbot]

The Buildbot has detected a failed build of Zope trunk 2.4 Windows 2000 
zc-bbwin.

Buildbot URL: http://buildbot.zope.org/

Build Reason: The web-page 'force build' button was pressed by '': 

Build Source Stamp: None
Blamelist: 

BUILD FAILED: failed test

sincerely,
 -The Buildbot

___
Zope-Dev maillist  -  Zope-Dev@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 )

Re: [Zope-dev] What use cases are driving make install from a checkout?

[Leonardo Rochael Almeida]

Just as a data point.

A lot of autoconf projects (the ones that made ./configure; make; make
install famous) don't just run like that from a checkout, but they are
never more than 2 steps away from that.

The process for a checkout is usually more like
./autoconf; ./automake; ./configure; make; make install

My point is: I don't think there's anything wrong in the install
procedure being different between the checkout and the tarball, but it
should never take more than a couple of fixed (and documented) steps to
convert a checkout to a tarball-equivalent environment, where
./configure; make; make install would work.

Cheers, Leo.

___
Zope-Dev maillist  -  Zope-Dev@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 )

Re: [Zope-dev] Re: buildbot failure in Zope branches 2.9 2.4 Windows 2000 zc-bbwin

[Tim Peters]

[Tim Peters]
 ...
 Failure in test test_checkPermission_proxy_roles_limit_access
 (AccessControl.tests.testZopeSecurityPolicy.C_ZSPTests)
 Traceback (most recent call last):
   File c:\python24\lib\unittest.py, line 260, in run
 testMethod()
   File 
 C:\buildbot\.org\zc-bbwin--Windows2000--Zope---trunk--2.4\build\lib\python\AccessControl\tests\testZopeSecurityPolicy.py,
 line 302, in test_checkPermission_proxy_roles_limit_access
 self.failIf(self.policy.checkPermission('Foo', r_item, context))
   File c:\python24\lib\unittest.py, line 305, in failIf
 if expr: raise self.failureException, msg
 AssertionError
 ...
 I don't have time to look at it.  Since the Windows buildbot slave
 `bbwin` doesn't have a C compiler, I suppose it's possible that the
 old, canned .pyd files it uses are out of synch with the current C
 code.

That was the problem.  Turns out `bbwin` does have a compiler, but the
buildbot recipe didn't use it.  After Jim fixed that, we have another
Windows-specific failure, in new code from ChrisM (this is on Zope
trunk, of course):

Failure in test test_get_env (ZServer.tests.test_clockserver.ClockServerTests)
Traceback (most recent call last):
  File c:\python24\lib\unittest.py, line 260, in run
testMethod()
  File C:\buildbot\.org\zc-bbwin--Windows
2000--Zope---trunk--2.4\build\lib\python\ZServer\tests\test_clockserver.py,
line 87, in test_get_env
self.assertEqual(env['PATH_TRANSLATED'], '/a /b')
  File c:\python24\lib\unittest.py, line 333, in failUnlessEqual
raise self.failureException, \
AssertionError: '\\a \\b' != '/a /b'
___
Zope-Dev maillist  -  Zope-Dev@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 )

[Zope-dev] Re: [RfC] Removal of old stuff in Zope 2.10

[Rocky Burt]

Max M wrote:
 If there is another practical way to do it, that would be fine too. I
 don't know about sqllite. But if it's more difficulte than dropping a
 package into a directory it would be bad.
 

Personally I'd be a huge proponent of including SQLite in zope core.  It
is extraordinarilly functional and has few requirements.  I particularly
like using it to ensure unit tests against RDBMS connections work
properly.  Requiring a user to install postgresql just to run the unit
tests of a product is somewhat unfeasible.

- Rocky



-- 
Rocky Burt
ServerZen Software -- http://www.serverzen.com
ServerZen Hosting -- http://www.serverzenhosting.net
News About The Server -- http://www.serverzen.net

___
Zope-Dev maillist  -  Zope-Dev@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 )

Re: [Zope-dev] Re: buildbot failure in Zope branches 2.9 2.4 Windows 2000 zc-bbwin

[Chris McDonough]

Hmmm... I *think* I just fixed this.


On Dec 21, 2005, at 3:48 PM, Tim Peters wrote:


[Tim Peters]

...
Failure in test test_checkPermission_proxy_roles_limit_access
(AccessControl.tests.testZopeSecurityPolicy.C_ZSPTests)
Traceback (most recent call last):
  File c:\python24\lib\unittest.py, line 260, in run
testMethod()
  File C:\buildbot\.org\zc-bbwin--Windows2000--Zope---trunk--2.4 
\build\lib\python\AccessControl\tests\testZopeSecurityPolicy.py,

line 302, in test_checkPermission_proxy_roles_limit_access
self.failIf(self.policy.checkPermission('Foo', r_item, context))
  File c:\python24\lib\unittest.py, line 305, in failIf
if expr: raise self.failureException, msg
AssertionError
...
I don't have time to look at it.  Since the Windows buildbot slave
`bbwin` doesn't have a C compiler, I suppose it's possible that the
old, canned .pyd files it uses are out of synch with the current C
code.


That was the problem.  Turns out `bbwin` does have a compiler, but the
buildbot recipe didn't use it.  After Jim fixed that, we have another
Windows-specific failure, in new code from ChrisM (this is on Zope
trunk, of course):

Failure in test test_get_env  
(ZServer.tests.test_clockserver.ClockServerTests)

Traceback (most recent call last):
  File c:\python24\lib\unittest.py, line 260, in run
testMethod()
  File C:\buildbot\.org\zc-bbwin--Windows
2000--Zope---trunk--2.4\build\lib\python\ZServer\tests 
\test_clockserver.py,

line 87, in test_get_env
self.assertEqual(env['PATH_TRANSLATED'], '/a /b')
  File c:\python24\lib\unittest.py, line 333, in failUnlessEqual
raise self.failureException, \
AssertionError: '\\a \\b' != '/a /b'



___
Zope-Dev maillist  -  Zope-Dev@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 )

[Zope-dev] buildbot failure in Zope trunk 2.4 Windows 2000 zc-bbwin

[buildbot]

The Buildbot has detected a failed build of Zope trunk 2.4 Windows 2000 
zc-bbwin.

Buildbot URL: http://buildbot.zope.org/

Build Reason: The web-page 'force build' button was pressed by '': 

Build Source Stamp: None
Blamelist: 

BUILD FAILED: failed failed slave lost

sincerely,
 -The Buildbot

___
Zope-Dev maillist  -  Zope-Dev@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 )

Re: [Zope-dev] zope-2.9 r40780 make install doesn't finish, files missing from bin

[Andrew Sawyers]

This has been my approach also.  Not surprisingly, many of us worked on
these processes together and have 'sanitized them' over time.  :)  There
has always been 'another side' who either hasn't liked this procedure or
the 'make' voodoo and have come up with their own, or just haven't had
to do this at all.

Andrew
 
 I really think there is not a single good reason for having a  
 different experience for checkouts vs tarballs. It would even lead to  
 major annoyance where I work right now, just to give a real life  
 example. For us, building out a development sandbox is the same  
 process as building out a production instance, and for development  
 buildouts we routinely want to just substitute checkous from a  
 different tag/branch of Zope.
 
 jens
 


___
Zope-Dev maillist  -  Zope-Dev@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 )

Re: [Zope-dev] Re: buildbot failure in Zope branches 2.9 2.4 Windows 2000 zc-bbwin

[Tim Peters]

[Tim Peters]
 ...
 That was the problem.  Turns out `bbwin` does have a compiler, but the
 buildbot recipe didn't use it.  After Jim fixed that, we have another
 Windows-specific failure, in new code from ChrisM (this is on Zope
 trunk, of course):

 Failure in test test_get_env
 (ZServer.tests.test_clockserver.ClockServerTests)
 Traceback (most recent call last):
   File c:\python24\lib\unittest.py, line 260, in run
 testMethod()
   File C:\buildbot\.org\zc-bbwin--Windows
 2000--Zope---trunk--2.4\build\lib\python\ZServer\tests
 \test_clockserver.py,
 line 87, in test_get_env
 self.assertEqual(env['PATH_TRANSLATED'], '/a /b')
   File c:\python24\lib\unittest.py, line 333, in failUnlessEqual
 raise self.failureException, \
 AssertionError: '\\a \\b' != '/a /b'

[Chris McDonough]
 Hmmm... I *think* I just fixed this.

Luckily for us, the buildbot doesn't give a rip what either of us
think.  Its judgment is that you _did_ fix it, and there's not a court
in the land that will convict you given that perfect defense.
___
Zope-Dev maillist  -  Zope-Dev@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 )

Re: [Zope-dev] zope-2.9 r40780 make install doesn't finish, files missing from bin

[Chris Withers]

Jens Vagelpohl wrote:


IMHO it is an important requirement. We're inviting a hailstorm of  
questions and annoyed users by breaking this well-known routine for  
checkouts.


I really think there is not a single good reason for having a  different 
experience for checkouts vs tarballs. It would even lead to  major 
annoyance where I work right now, just to give a real life  example. For 
us, building out a development sandbox is the same  process as building 
out a production instance, and for development  buildouts we routinely 
want to just substitute checkous from a  different tag/branch of Zope.


Big +1, and that's not just 'cos I work with Jens ;-)

Chris

--
Simplistix - Content Management, Zope  Python Consulting
   - http://www.simplistix.co.uk
___
Zope-Dev maillist  -  Zope-Dev@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 )

Re: [Zope-dev] Re: [RfC] Removal of old stuff in Zope 2.10

[Chris Withers]

Jeff Kowalczyk wrote:

Andreas Jung wrote:


I'll raise the question again: what are the benefits of the HelpSys for
a Zope user?



I can't recall clicking on top frame of the ZMI or a 'Help!' link in the
past few years, either. Perhaps an equivalent or greater benefit would be
to rip out locally installed static help facilities, and spend the effort
migrating* zope.org to a plone version that could run PloneHelpCenter:

http://plone.org/documentation


FWIW, I think storing docs anywhere on the filesystem and in the product 
distribution is absolutely 100% evil.


You asking product authors to commit to a url being around forever, and 
that's unreasonable and foolish...


Chris

--
Simplistix - Content Management, Zope  Python Consulting
   - http://www.simplistix.co.uk

___
Zope-Dev maillist  -  Zope-Dev@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 )

Re: [Zope-dev] What use cases are driving make install from a checkout?

[Fred Drake]

On 12/21/05, Leonardo Rochael Almeida [EMAIL PROTECTED] wrote:
 My point is: I don't think there's anything wrong in the install
 procedure being different between the checkout and the tarball, but it
 should never take more than a couple of fixed (and documented) steps to
 convert a checkout to a tarball-equivalent environment, where
 ./configure; make; make install would work.

How important is the convert aspect of this?  Would creating a new
tree that supports ./configure; make; make install seem reasonable
to you?

If so, zpkg -t -C releases/Zope.cfg would create the tree, and cd
Zope-0.0.0 would make that the current directory.

There is a hidden difference here, however:  the new tree would be a
Zope 3 release, and would not typically contain everything in the
checkout.


  -Fred

--
Fred L. Drake, Jr.fdrake at gmail.com
There is no wealth but life. --John Ruskin
___
Zope-Dev maillist  -  Zope-Dev@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 )

Re: [Zope-dev] [ZPublisher] specifiying 'charset' for the content-type header

[Andreas Jung]

--On 21. Dezember 2005 18:07:49 + Chris Withers 
[EMAIL PROTECTED] wrote:


How will Zope know when _not_ to add the content-type header?


Makes no sense to me. Either the application set the content-type header or 
Zope does it for you. Check HTTPResponse.py.




How will Zope tell if the charset is undefined and what does
undefined mean in this context?


The HTTP spec says that a http server *can* set the charset to make the 
encoding of the payload clear. That's what we are doing now. Not specifying 
the charset means for the browser: *guessing* the encoding which means the 
browser defaults to some unspecified default encoding.


-aj

pgp7xgHZLLdbH.pgp
Description: PGP signature
___
Zope-Dev maillist  -  Zope-Dev@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 )

Re: [Zope-dev] Re: [RfC] Removal of old stuff in Zope 2.10

[Andreas Jung]

--On 21. Dezember 2005 17:23:26 -0330 Rocky Burt [EMAIL PROTECTED] 
wrote:




Personally I'd be a huge proponent of including SQLite in zope core.  It
is extraordinarilly functional and has few requirements.  I particularly
like using it to ensure unit tests against RDBMS connections work
properly.  Requiring a user to install postgresql just to run the unit
tests of a product is somewhat unfeasible.



Do you volunteer to take over the responsibility for this project?

That means:

- integrate the python bindings
- integrate the DA
- if necessary update existing documentation
- convince someone from ZC to import the Sqlite code base on svn.zope.org
  (since Sqlite is _not_ ZPL only a ZC employee is permitted to import 
non-ZPL code).



-aj



pgpUMN2csL00N.pgp
Description: PGP signature
___
Zope-Dev maillist  -  Zope-Dev@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 )

[Zope-dev] buildbot failure in Zope trunk 2.4 Linux zc-buildbot

[buildbot]

The Buildbot has detected a failed build of Zope trunk 2.4 Linux zc-buildbot.

Buildbot URL: http://buildbot.zope.org/

Build Reason: changes
Build Source Stamp: 2419
Blamelist: andreasjung

BUILD FAILED: failed test

sincerely,
 -The Buildbot

___
Zope-Dev maillist  -  Zope-Dev@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 )

Re: [Zope-dev] [RfC] Removal of old stuff in Zope 2.10

[Dario Lopez-Kästen]

Chris Withers wrote:

Andreas Jung wrote:


I've never met ppl who actually used the HelpSys so that's why I am 
raising the question about the value of the HelpSys. Lots of my 
co-workers work with Zope on different levels (scripters, product 
developers)...I've always pointed them to the Zope Book...the HelpSys 
was never a topic.



I most commonly use the HurtSys for DateTime's api, and some of the 
idnexing apis. That said, I also agree it should die if something nicer 
comes along ;-)




I use it a lot, and like Chris, for the DateTime stuff, but also for 
looking up how to manage properties, etc. It is/was a big help for me 
(more so than the zope book, at least when I was learning Zope) when 
learning stuff and looking up things.


One difference I perceive (YMMV) between the Zope book and the Online 
help is that the online help is more of a renference than the Zope book.


I think my point is that it is an added value if there is an online help 
available that does not require a live connection to the internet every 
time you need to look something up.


So +1 on killing the current helpsystem and +1 on replacing it with 
something nicer :-)



Sincerely,
/dario

--
-- ---
Dario Lopez-Kästen, IT Systems  Services Chalmers University of Tech.
Lyrics applied to programming  application design:
emancipate yourself from mental slavery - redemption song, b. marley

___
Zope-Dev maillist  -  Zope-Dev@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 )

[Zope-dev] buildbot failure in Zope trunk 2.4 Windows 2000 zc-bbwin

[buildbot]

The Buildbot has detected a failed build of Zope trunk 2.4 Windows 2000 
zc-bbwin.

Buildbot URL: http://buildbot.zope.org/

Build Reason: changes
Build Source Stamp: 2419
Blamelist: andreasjung

BUILD FAILED: failed test

sincerely,
 -The Buildbot

___
Zope-Dev maillist  -  Zope-Dev@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 )

Re: [Zope-dev] zope-2.9 r40780 make install doesn't finish, files missing from bin

[Dario Lopez-Kästen]

Jens Vagelpohl wrote:


On 21 Dec 2005, at 18:47, Jim Fulton wrote:


I'll note, FWIW, that we don't do installs from Zope 3 checkouts.
I think it's worth asking whether this is an important requirement.
If it is, then we should make it work.  Question is, is it worth
delaying the release?  I don't know.



IMHO it is an important requirement. We're inviting a hailstorm of  
questions and annoyed users by breaking this well-known routine for  
checkouts.


I really think there is not a single good reason for having a  different 
experience for checkouts vs tarballs. It would even lead to  major 
annoyance where I work right now, just to give a real life  example. For 
us, building out a development sandbox is the same  process as building 
out a production instance, and for development  buildouts we routinely 
want to just substitute checkous from a  different tag/branch of Zope.




+1 on this.
It is important for us in the forced to be both developer and deployer 
by evil sysadmins camp.


/dario

--
-- ---
Dario Lopez-Kästen, IT Systems  Services Chalmers University of Tech.
Lyrics applied to programming  application design:
emancipate yourself from mental slavery - redemption song, b. marley

___
Zope-Dev maillist  -  Zope-Dev@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 )

[Zope] Re: a binary of zope for debian

[Maik Ihde]

adeline nombre [EMAIL PROTECTED] writes:

   Hi.  it's me again. I'm in trouble.  Can somebody tell me where to fin a
binary of zope for debian which can be run with python2.3. ?  thank you very 
much

If you want an actual Zope version you will need to install it from source,
which is very easy to do.

Debian Sarge also has a zope2.7 (That is Zope 2.7.5 if I am not mistaken)
package, which can be installed via apt if that is what you want. However the
latest stable 2.x is 2.8.5 ...

Regards
Maik




___
Zope maillist  -  Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope-dev )

[Zope] FTP rights problem

[Martin Koekenberg]

Hello,



When a user connects with FTP to a Zope folder with only rights onthat 
subfolder he can'tcreate a folder or delete files.He 
hasthe Manager role and all the rights.



Is this a bug or doI have to give this user Manager rights to the root 
of the zope instance ?

Or is there an other solution to get the FTP working ?



Regards,



Martin Koekenberg







___
Zope maillist  -  Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope-dev )

Re: [Zope] Zope, Apache, REMOTE_USER

[Jens Vagelpohl]

I think you missed the point. The main reason to ditch it is the fact  
that there is no one who is willing and able to support the code for  
it in Zope. Just because someone comes up with a combination where  
FCGI might have a benefit still does not give us a developer to  
support it.


jens

On 21 Dec 2005, at 04:48, David Bear wrote:


could this be one reason to keep fastcgi?

On 12/19/05, Robert Boyd [EMAIL PROTECTED] wrote: I'm using  
Apache 2.0, and I cannot find a solution to passing the

value of REMOTE_USER from Apache to Zope when using a rewrite rule. I
have Apache rewriting requests for Zope, and hooked into Tomcat with
mod_jk. My users login through a servlet, and Apache has REMOTE_USER
available to it. But any subsequent request to Zope loses this value.
I used to have this all working when using FastCGI, but I'm hoping to
use only mod_rewrite. Is it possible?

Thanks,
Rob

___
Zope maillist  -   Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope-dev )





--
David Bear
What's the difference between private knowledge and public knowledge?
___
Zope maillist  -  Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists -
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope-dev )


___
Zope maillist  -  Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists - 
http://mail.zope.org/mailman/listinfo/zope-announce

http://mail.zope.org/mailman/listinfo/zope-dev )

Re: [Zope] question for anyone using apache on windows

[Chris Withers]

I'm sure there's an Apache list you could be asking these questions, 
this has nothing to do with Zope.


#apache on irc.freenode.net is where I'd go ;-)

Chris

michael nt milne wrote:

Hi

Ok so I looked at this stuff but can't find anything listed for point 3.
Also I had to set Plone to listen on 8080 within its config file and now get
Apache for my Plone domains. However they won't re-direct to the right site
within the Plone installation. I've achieved this on Unix with the virtual
host stuff below.


   1. Find the httpd.conf file (usually you will find it in a folder
   called conf, config or something along those lines)
   2. Inside the httpd.conf file uncomment the line *LoadModule
   rewrite_module modules/mod_rewrite.so* (remove the pound '#' sign from
   in front of the line)
   3. Also find the line *ClearModuleList* is uncommented then find and
   make sure that the line *AddModule mod_rewrite.c* is not commented
   out.



NameVirtualHost ip:80
VirtualHost ip:80
ServerName name
RewriteEngine On
RewriteRule ^/(.*)
http://ip:8080/VirtualHostBase/http/name:80/site/Virt
ualHostRoot/$1 [L,P]
/VirtualHost




On 12/19/05, michael nt milne [EMAIL PROTECTED] wrote:


ok, i simply downloaded the Apache 2.0.55 release for Windoes from Apache.
Thre RewriteEngine is set to on in the httpd.conf. God knows why the
module wouldn't be available in the distribution. Do you know any
documentation on how to install on module at all? The unix version comes
with it by default I think. **

On 12/19/05, Andreas Jung [EMAIL PROTECTED] wrote:


Likely the rewrite module isn't loaded (check the corresponding
LoadModule
statements of your configuration).

-aj

--On 19. Dezember 2005 16:33:59 + michael nt milne
 [EMAIL PROTECTED] wrote:



Does RewriteEngine work on Apache for Windows 2.0.5 ?

I'm getting the following..

Syntax error on line 960 of C:/Program Files/Apache
Group/Apache2/conf/httpd.con
f:
Invalid command 'RewriteEngine', perhaps mis-spelled or defined by a
module not
included in the server configuration
Note the errors or messages above, and press the ESC key to


exit.  22...




NameVirtualHost ip:80
VirtualHost ip:80
ServerName name
RewriteEngine On
RewriteRule ^/(.*)
http://ip:8080/VirtualHostBase/http/name:80/site/Virt
ualHostRoot/$1 [L,P]
/VirtualHost












___
Zope maillist  -  Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce

 http://mail.zope.org/mailman/listinfo/zope-dev )


--
Simplistix - Content Management, Zope  Python Consulting
   - http://www.simplistix.co.uk
___
Zope maillist  -  Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists - 
http://mail.zope.org/mailman/listinfo/zope-announce

http://mail.zope.org/mailman/listinfo/zope-dev )

[Zope] zope db question

[José Carlos Senciales Chaves]

Hi

Iam new phyton and zope 
programmer.

Ihave to make a product for zope and i must 
use a list of groups with a lot of data.

I´m wondering if i must to use a list of persistent 
objects or if it´s better use a database like 
gadfly with tables or another one. 

I´m a little confuse. I think that the two 
solutions are possible but i don´t know whitch is better.

sorry for my bad english.

thanks.
jose from Spain, 
Europe.
___
Zope maillist  -  Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope-dev )

Re: [Zope] error installing zope from source

[Martijn Pieters]

On 12/20/05, adeline nombre [EMAIL PROTECTED] wrote:
 the problem now is that when I do make there is this error message: does
 not find file /usr/lib/python2.3/config/Makefile . And when
 I look in /usr/lib/python2.3/ , there is no directory config.
 I have python2.3.
 my OS is debian sarge.

Install the python2.3-dev package.

--
Martijn Pieters
___
Zope maillist  -  Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope-dev )

Re: [Zope] More on understanding conflicts

[Maciej Wisniowski]

There are two distinct sections to the navigation_box transaction.  One
where the session variables are read and a second where they are used. To
minimize conflicts, the what is now a single tranaction should be split 
into two separate transactions.


Any thought as to how to do that?  If navigation_box were broken into 
two separate methods, say nav_box1 and nav_box2, how does nav_box1 
commit itself and then transfer control and data (a session variable 
snapshot) to nav_box2 as a new transaction? 

I would guess that if nav_box1 redirects to nav_box2 a new transaction 
is initiated and the old one committed.  Is that correct?  And is there 
a better way to get the same effect?
 


Hi
You've written in your first post that you're dealing with read conflict 
errors

so I think transaction commiting is not the point here - it would cause
write conflict. Am I right?

I think that few simple things you can do is using external method 
instead of

your's python script getSessionVariable (to make it faster) and redesigning
it's code that it returns (at once) for example a dictionary filled with 
requested

values from session. Maybe you can use external method to generate whole
navigation. The best thing would be to write product but this is a bit 
more work,

and I think external methods are much faster to check in your situation.

Other thing you can do is to use ZopeProfiler to see exactly what is called
when the page is requested and how long it takes.

Other quick solution, which may not be appropiate in your case, is to
render navigation box once and store whole the generated code in session.

--
Maciej Wisniowski
___
Zope maillist  -  Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists - 
http://mail.zope.org/mailman/listinfo/zope-announce

http://mail.zope.org/mailman/listinfo/zope-dev )

Re: [Zope] zope db question

[Andreas Jung]

--On 21. Dezember 2005 11:09:14 +0100 José Carlos Senciales Chaves 
[EMAIL PROTECTED] wrote:



Hi

I am new phyton and zope programmer.

I have to make a product for zope and i must use a list of groups with a
lot of data.

I´m wondering if i must to use a list of persistent objects or if it´s
better use a database like  gadfly with tables or another one.


Gadfly is likely to be removed in one of the next Zope versions.
RBDMS vs. ZODB ...that really depends on your usecase. lots of data is 
nothing useful for making a decision.


-aj

pgpBr9JGvGvKu.pgp
Description: PGP signature
___
Zope maillist  -  Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope-dev )

Re: [Zope] More on understanding conflicts

[Chris McDonough]

Write conflicts happen for a transaction.  In Zope, there is one
transaction per request.


There are two distinct sections to the navigation_box transaction.


There's a transaction for something named navigation_box?  Is this  
an IFRAME?



  One
where the session variables are read and a second where they are  
used. To
minimize conflicts, the what is now a single tranaction should be  
split

into two separate transactions.


Are you maybe misusing the term transaction here?  If this logic  
all happens in the course of a single request, it all happens in the  
same transaction unless that request causes, say, the reload of a frame.


There is a concept of a transaction here.  But it doesn't have  
anything to do with what happens during the course of a single  
request unless you explicitly try to control transactions, which is  
almost never a good idea.



Any thought as to how to do that?  If navigation_box were broken into
two separate methods, say nav_box1 and nav_box2, how does nav_box1
commit itself and then transfer control and data (a session variable
snapshot) to nav_box2 as a new transaction?


I suspect I don't understand what this would achieve.  Having more  
transactions will cause more conflicts.  Conflicts happen as a result  
of conflicting changes in two transactions.



I would guess that if nav_box1 redirects to nav_box2 a new transaction
is initiated and the old one committed.  Is that correct?  And is  
there

a better way to get the same effect?


I have no idea, sorry.

I think maybe what you might want to do here is to not use builtin  
Zope sessions. ;-)  Zope sessions rely on ZODB and are  
transactional.  If they didn't rely on ZODB, you wouldn't be getting  
conflict errors.  If they weren't transactional, you probably  
wouldn't notice.


Might be time to cut bait here.  We've been talking about this for  
months. ;-)  I think someone wrote a relational database backend for  
the sessioning API some time ago.  You may want to give that a shot.


- C

___
Zope maillist  -  Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists - 
http://mail.zope.org/mailman/listinfo/zope-announce

http://mail.zope.org/mailman/listinfo/zope-dev )

[Zope] Re: zope db question

[Rocky Burt]

Hi José,

If you're learning how to use Zope then it'd be best (imho) for you to
learn how to do it with the ZODB (this is the 'default' way to store
data persistently in Zope).  Later on if you have a specific reason to
put this in a relational database (please, don't use gadfly) then it'll
be much easier for you to figure this out.

- Rocky


José Carlos Senciales Chaves wrote:
 Hi
  
 I am new phyton and zope programmer.
  
 I have to make a product for zope and i must use a list of groups with a
 lot of data.
  
 I´m wondering if i must to use a list of persistent objects or if it´s
 better use a database like
 gadfly with tables or another one.
  
 I´m a little confuse. I think that the two solutions are possible but i
 don´t know whitch is better.
  
 sorry for my bad english.
  
 thanks.
 jose from Spain, Europe.
 
 
 
 
 ___
 Zope maillist  -  Zope@zope.org
 http://mail.zope.org/mailman/listinfo/zope
 **   No cross posts or HTML encoding!  **
 (Related lists - 
  http://mail.zope.org/mailman/listinfo/zope-announce
  http://mail.zope.org/mailman/listinfo/zope-dev )


-- 
Rocky Burt
ServerZen Software -- http://www.serverzen.com
ServerZen Hosting -- http://www.serverzenhosting.net
News About The Server -- http://www.serverzen.net

___
Zope maillist  -  Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope-dev )

Re: [Zope] More on understanding conflicts

[Chris Withers]

Dennis Allison wrote:

Ah so desu.  That's the conceptual hook I was missing.  Only one
transaction per request and no subtransactions!  


ZODB substransactions won't help you here in the slightest...


A transaction is
processing initiated by a client request or a redirect. (Anything else?)  
A transaction has its own REQUEST and RESPONSE objects.


Wrong way round. Each REQUEST has one RESPONSE associated with it, and 
the publisher does either a transaction commit, if no errors occur, or a 
transaction abort, if errors occur, once it has processed a REQUEST. 
Read conflict errors can be raised at any time, but shouldn't really 
occur once you have MVCC working. Write conflict errors only happen 
during transaction commit. The publisher retries the whole request if a 
conflict errors of either sort occurs. If the retry fails 3 times, it 
gives up, aborts the transaction and reports the conflict error to the 
end user by way of writing to the response object.


hth,

Chris

--
Simplistix - Content Management, Zope  Python Consulting
   - http://www.simplistix.co.uk
___
Zope maillist  -  Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists - 
http://mail.zope.org/mailman/listinfo/zope-announce

http://mail.zope.org/mailman/listinfo/zope-dev )

Re: [Zope] More on understanding conflicts

[Chris McDonough]

On Dec 21, 2005, at 10:32 AM, Dennis Allison wrote:

Thanks again Chris for the helpful comments.

The navigation_box, in this context is just a table which is rendered
into a frame in our standard frameset.  It is not an iframe.


So you do use frames!  That's a huge clue.  I wish I didn't feel like  
I had to drag that out of you. :-(


In the sense I used them below, a transaction and a request are the  
same

thing.  This follows from the fact that each request is managed as a
single transaction.  Perhaps it would have been a better choice of  
words

to use request.

I suggested breaking the request into two requests as one way to help
manage conflicts.  Only the first part of the the split request would
reference the session variables, so the window of opportunity for a
session variable conflict would be smaller even though the number of
requests is larger.


This is probably not really a reasonable thing to do.  A request is  
generated by a user agent.  With a lot of deep dark magic, you *can*  
generate a request from within Zope that makes it appear that it  
comes from the outside, but it's not easy and unhelpful here.   
Remember what I said about the write on read pattern of sessions?   
it doesn't matter if you're only reading session data.  There still  
may be writes happening.   Breaking things up into more requests will  
not help.


What you want to do instead is *not access the same session from two  
different requests at the same time*.  You probably know this, but  
when a frameset is used, the browser generates N requests... one per  
frame.  These requests happen at about the same time whenever the  
frameset is accessed by a user.  Moreover, since the requests come  
from the same browser, the session identifier for both requests is  
the same.


By accessing session data from code within more than one frame, you  
are essentially creating a situation where at least two different  
threads will always be accessing the very same session object  
whenever the frameset is rendered.  For as many frames as are in the  
frameset, if the code that renders each frame access the session, a  
transaction will touch the same session data object and perhaps some  
shared housekeeping data structures.  It's as if you're pressing the  
refresh button in rapid succession on a page that accesses session  
data.  This is prime area for a conflict.


And, sigh, you are probably right--it may be time to abandon the  
standard

release session implementation and roll our own.


This is still a reasonable thing to do, but if you can get away with  
using sessions in only *one* of the pages of your frameset, things  
will get much better.


- C

___
Zope maillist  -  Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists - 
http://mail.zope.org/mailman/listinfo/zope-announce

http://mail.zope.org/mailman/listinfo/zope-dev )

Re: [Zope] More on understanding conflicts

[Chris McDonough]

On Dec 21, 2005, at 11:38 AM, Dennis Allison wrote:



Chris,

You asked about frames a while back and I responded in the  
affirmative.
I am sure I mentioned that we use frames and framesets and  
explained that
we use a bit of Javascript to manage loading individual frames  
rather than

loading the entire frameset whenever possible.


Eek.  Sorry, I don't remember this.  Context is hard to keep over the  
course of several weeks/months, of course.  And my brain is going  
with my age.  I don't mean to be a nag (really, I understand this is  
hard), but I asked two emails ago do you use frames? and you didn't  
answer that question directly in your response at all; only by way of  
teasing it out of you by asking if it was an IFRAME in a followup was  
the fact that this app is a frame-based one re-revealed to me.   In  
general, it would be very helpful if you could answer the questions  
that are asked when they're asked even if they reveal the fact that  
I'm a doddering old man and can't remember things from moment to  
moment,  Otherwise it's difficult (and honestly a bit frustrating) to  
try to help you.


In any case, typically the problem with frames only reveals itself  
when the entire frameset is loaded or the body of one frame causes  
the other frames to load.  Your javascript may not be helping here...  
it could be hurting.  For example, if a user reloads the main frame  
(say as a result of a POST request) and by doing so, during its re- 
rendering, it causes two other frames to refresh themselves due to an  
inline script function in the body of the main frame, that's the  
moral equivalent of reloading the frameset entirely.  You have a tiny  
bit more control, e.g. maybe you could set a Javscript timer to  
reload the other frames in a staggered way where you reload one,  
then the other after a certain number of seconds.  But otherwise it's  
the same problem.  Hard to know what's going on there.



  Still, your point about
the multiple threads due to the requests from individual frames when a
frameset gets rendered is a valid one and one I have not given the  
weight

it deserves.

Issues around multiple threads and concurrency is going to be more and
more of a problem as we move to smarter clients and AJAX-like
implementations.


Smart clients perhaps.  But Ajax is supposed to allow you to do  
interesting things *without* reloading the page, and because (to my  
knowledge) no current Javascript implementation can make a request  
asynchronously, so you can only make one request at a time from  
within a given browser document.  So using Ajax shouldn't cause  
*more* conflicts; it should cause fewer.  Unless of course your Ajax  
calls emanate from different frames (different DOM documents).   
Then you're back in the same boat (depending on the Javascript  
implementation, I suppose).  It's really a problem with frames (or  
more generally, multiple documents at the same time) rather than with  
Ajax.



It looks like there are several small things I can do to improve the
present system's conflict rate, but, absent some major structural  
changes,
I won't be able to drive them to O(zero).  Fortunately, while the  
level of

conflicts is high, they are infrequent relative to the number of hits
served, and most are resolved by the normal Zope conflict resolution
mechanism.


Well, that's good.  Does that mean I'm off the hook? ;-)

- C


___
Zope maillist  -  Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists - 
http://mail.zope.org/mailman/listinfo/zope-announce

http://mail.zope.org/mailman/listinfo/zope-dev )

Re: [Zope] More on understanding conflicts

[Dennis Allison]

Chris W,

The issue here has had to do with session variables and their iteraction
with the persistence mechanism and conflicts and multiple threads for the
same session.  Chris McDonough has pointed out that session variables can
cause writes and write conflicts even if the only Zope level access is a
read.  I thought MVCC works out of the box for Zope 2.8.4 which uses ZODB
2.3.4. Am I wrong?

The real surprise was that you can get a write conflict from a pair of
session variable reads!

Sorry, I wasn't all that clear when I had my epiphany about REQUEST and
transactions.  You said it much more clearly and precisely.  Since
conflict errors are discovered and managed when the publisher commits,
there is not a whole lot one can do, in terms of code organization, to
minimize the potential for conflicts.

Thanks for your insight.

On Wed, 21 Dec 2005, Chris Withers wrote:

 Dennis Allison wrote:
  Ah so desu.  That's the conceptual hook I was missing.  Only one
  transaction per request and no subtransactions!  
 
 ZODB substransactions won't help you here in the slightest...
 
  A transaction is
  processing initiated by a client request or a redirect. (Anything else?)  
  A transaction has its own REQUEST and RESPONSE objects.
 
 Wrong way round. Each REQUEST has one RESPONSE associated with it, and 
 the publisher does either a transaction commit, if no errors occur, or a 
 transaction abort, if errors occur, once it has processed a REQUEST. 
 Read conflict errors can be raised at any time, but shouldn't really 
 occur once you have MVCC working. Write conflict errors only happen 
 during transaction commit. The publisher retries the whole request if a 
 conflict errors of either sort occurs. If the retry fails 3 times, it 
 gives up, aborts the transaction and reports the conflict error to the 
 end user by way of writing to the response object.
 
 hth,
 
 Chris
 
 

-- 

___
Zope maillist  -  Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope-dev )

[Zope] Zope/CMF developer required

[FAIRS, Dan, FM]

Hi,

The Royal Bank of Scotland is looking to recruit a contract developer to
join the Corporate Markets Content Management System development team. 

The successful candidate will meet or exceed the following requirements: 
- 3 years experience developing with Python, Zope and the CMF
- 3 years working with standards-compliant HTML and CSS
- 1 year developing on and administering Red Hat Linux (preferably RHEL) and
Apache
- Demonstrable experience of working with and scaling high volume Zope sites
- Understanding of the OSS model, with evidence of working with the
community

The following experience is also useful:
- Development with Plone and Archetypes
- Zope 3 development experience
- JavaScript development experience
- Experience with Subversion
- Experience developing accessible web sites; in particular with UK DDA
legislation and WAI standards
- Exposure to test-first methodologies

The successful candidate will be able to communicate with both technical and
non-technical users, and will be expected to undertake tasks such as
requirements gathering, coding, troubleshooting, and peer review.

The role is based in Central London (UK) to start early 2006. Rate in the
region of £370/day.

If you are interested, please mail your CV/resume to me -
[EMAIL PROTECTED] I shall aim to respond during January 2006.

Cheers,
Dan 

--
[EMAIL PROTECTED] | FM IT | Royal Bank of Scotland plc



***
The Royal Bank of Scotland plc. Registered in Scotland No 90312.  Registered 
Office: 36 St Andrew Square, Edinburgh EH2 2YB. 
 
Authorised and regulated by the Financial Services Authority 
 
This e-mail message is confidential and for use by the  
addressee only. If the message is received by anyone other 
than the addressee, please return the message to the sender  
by replying to it and then delete the message from your
computer. Internet e-mails are not necessarily secure. The   Royal 
Bank of Scotland plc does not accept responsibility for  
changes made to this message after it was sent.  


Whilst all reasonable care has been taken to avoid the   
transmission of viruses, it is the responsibility of the recipient to
ensure that the onward transmission, opening or use of this 
message and any attachments will not adversely affect its   
systems or data.  No responsibility is accepted by The Royal   
Bank of Scotland plc in this regard and the recipient should carry   
out such virus and other checks as it considers appropriate.   

   Visit our websites at:   
   
http://www.rbs.co.uk/CBFM   
 
http://www.rbsmarkets.com   
  

   


___
Zope maillist  -  Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists -
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope-dev )

Re: [Zope] More on understanding conflicts

[Chris McDonough]

On Dec 21, 2005, at 12:40 PM, Dennis Allison wrote:



Chris W,

The issue here has had to do with session variables and their  
iteraction
with the persistence mechanism and conflicts and multiple threads  
for the
same session.  Chris McDonough has pointed out that session  
variables can
cause writes and write conflicts even if the only Zope level access  
is a
read.  I thought MVCC works out of the box for Zope 2.8.4 which  
uses ZODB

2.3.4. Am I wrong?


It does.  But MVCC does not prevent write conflicts.  Only read  
conflicts.




The real surprise was that you can get a write conflict from a pair of
session variable reads!


That is surprising, no doubt. ;-)

___
Zope maillist  -  Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists - 
http://mail.zope.org/mailman/listinfo/zope-announce

http://mail.zope.org/mailman/listinfo/zope-dev )

Re: [Zope] More on understanding conflicts

[Dennis Allison]

On Wed, 21 Dec 2005, Chris McDonough wrote:

 On Dec 21, 2005, at 11:38 AM, Dennis Allison wrote:
 
 
  Chris,
 
  You asked about frames a while back and I responded in the  
  affirmative.
  I am sure I mentioned that we use frames and framesets and  
  explained that
  we use a bit of Javascript to manage loading individual frames  
  rather than
  loading the entire frameset whenever possible.
 
 Eek.  Sorry, I don't remember this.  Context is hard to keep over the  
 course of several weeks/months, of course.  And my brain is going  
 with my age.  I don't mean to be a nag (really, I understand this is  
 hard), but I asked two emails ago do you use frames? and you didn't  
 answer that question directly in your response at all; only by way of  
 teasing it out of you by asking if it was an IFRAME in a followup was  
 the fact that this app is a frame-based one re-revealed to me.   In  
 general, it would be very helpful if you could answer the questions  
 that are asked when they're asked even if they reveal the fact that  
 I'm a doddering old man and can't remember things from moment to  
 moment,  Otherwise it's difficult (and honestly a bit frustrating) to  
 try to help you.

Sorry if I appeared unresponsive--the fact that we use frames is hardly a 
secret.   I suppose that it would be helpful to make up soem summary of 
features for ongoing threads like this one.  

 
 In any case, typically the problem with frames only reveals itself  
 when the entire frameset is loaded or the body of one frame causes  
 the other frames to load.  Your javascript may not be helping here...  
 it could be hurting.  For example, if a user reloads the main frame  
 (say as a result of a POST request) and by doing so, during its re- 
 rendering, it causes two other frames to refresh themselves due to an  
 inline script function in the body of the main frame, that's the  
 moral equivalent of reloading the frameset entirely.  You have a tiny  
 bit more control, e.g. maybe you could set a Javscript timer to  
 reload the other frames in a staggered way where you reload one,  
 then the other after a certain number of seconds.  But otherwise it's  
 the same problem.  Hard to know what's going on there.

By convention the primary content frame does not cause other frames to 
re-render but there are multiple implementors and creaping featurism
which may have changed that.  The navigation_box frame we have been 
discussion gets re-rendered on a navigation change (duh) and may initiate
re-rendering of a tabs_frame.  Except for the full frameset rendering,
we are likely to be fairly conflict clean.  I can look in the logs and 
tell...  Might be interesting.


Still, your point about
  the multiple threads due to the requests from individual frames when a
  frameset gets rendered is a valid one and one I have not given the  
  weight
  it deserves.
 
  Issues around multiple threads and concurrency is going to be more and
  more of a problem as we move to smarter clients and AJAX-like
  implementations.
 
 Smart clients perhaps.  But Ajax is supposed to allow you to do  
 interesting things *without* reloading the page, and because (to my  
 knowledge) no current Javascript implementation can make a request  
 asynchronously, so you can only make one request at a time from  
 within a given browser document.  So using Ajax shouldn't cause  
 *more* conflicts; it should cause fewer.  Unless of course your Ajax  
 calls emanate from different frames (different DOM documents).   
 Then you're back in the same boat (depending on the Javascript  
 implementation, I suppose).  It's really a problem with frames (or  
 more generally, multiple documents at the same time) rather than with  
 Ajax.

I did not know that XMLHttp interactions were asynchronous but serialized.  
Most browsers can make multiple simultaneous requests so I'd assumed that 
XMLHttp would just grab a connection and go and that multiple requests 
can be in progress simultaneously.

  It looks like there are several small things I can do to improve the
  present system's conflict rate, but, absent some major structural  
  changes,
  I won't be able to drive them to O(zero).  Fortunately, while the  
  level of
  conflicts is high, they are infrequent relative to the number of hits
  served, and most are resolved by the normal Zope conflict resolution
  mechanism.
 
 Well, that's good.  Does that mean I'm off the hook? ;-)

Not really off the hook as issues still remain and you are a valuable
resource.  :-)  I need to spend some time thinking about the issues an do
some cautious experimentation and testing.  


 

___
Zope maillist  -  Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope-dev )

Re: [Zope] More on understanding conflicts

[Michael Dunstan]

On 12/22/05, Dennis Allison [EMAIL PROTECTED] wrote:
 The issue here has had to do with session variables and their iteraction
 with the persistence mechanism and conflicts and multiple threads for the
 same session.  Chris McDonough has pointed out that session variables can
 cause writes and write conflicts even if the only Zope level access is a
 read.  I thought MVCC works out of the box for Zope 2.8.4 which uses ZODB
 2.3.4. Am I wrong?

 The real surprise was that you can get a write conflict from a pair of
 session variable reads!

The missing detail here is that reading a session object causes a
write to the database to update the last access time for that session
object. So what looks like a plain old read to the application code
above, in-fact includes a write just below the surface. (This is a
design choice so that stale session objects can be removed.)

There are implementation details of TransientObject that attempt to
mitigate some of the pain:

- The access time has a WRITEGRANULARITY. That can help a bit by
avoiding writing altogether some of the time. But still there is need
to write (and so potential contention) each time a boundary of that
granularity is crossed.

- And _p_resolveConflict of TransientObject will most often pick a
state to avoid a conflict error. When it does there is the performance
cost of writing to database but there will be no ConflictError.
However, I've suggested in the past that you should comment out
_p_resolveConflict while debugging consistency problems. What is the
current state of your _p_resolveConflict now? _p_resolveConflict
includes a DIWM'ly component. Perhaps you still need to avoid that
component of _p_resolveConflict? In that case a _p_resolveConflict
could be engineered that can resolve the case of just updates to the
access time? But still bails out when presented with two states that
have explicit updates to maintain consistency.

Though that's all just conjecture till we see your tracebacks for your
conflicts.

michael
___
Zope maillist  -  Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists -
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope-dev )

Re: [Zope] How to make good architecture in Zope2?

[Roman Suzi]

Lennart Regebro wrote:


On 12/20/05, Roman Suzi [EMAIL PROTECTED] wrote:
 


Lets suppose that I've done OO Analysis and have a dozen of nice classes
which model my problem domain. Lets also suppose that I did it on the
basis of known use cases. Now I want to build Web application fulfilling
those use cases but  separate my  classes from Zope framework (Ok,  some
of them could be taken from Zope framework, like user folder), so that I
can see the problem domain abstractions in the clear, without a mess of
miriads of Presentation injections.
(I'd liked to put presentation-related things into other classes and ZPTs)

Are there any good examples out there, or any good architectural
solutions for that?
   



Yes. Zope 3. ;)
Zope 3 adresses several of these questions, especially the separation
of presentation from logic on a class bases. And of you can't use Zope
3, then you can use the same principals under Zope 2 thanks to the
Five technology:
http://codespeak.net/z3/five/

Five is included with Zope 2 since Zope 2.8.
 



Thank you for hints, Lennart. They are quite helpful. Its hard for me to 
competently say anything more on this as some time is required to

learn and try Five.

 


Or is it even possible in Zope2 to go that far
without doing to much adaptation?
   



No problems at all. Nuxeos new calendar product is done exactly like
that, even to the point that the base classes are in a separate
product (CalCore) that could be used outside of Zope, the UI is in
another product (CalZope) that provides all the pages, and we have
integration with CPS in a third product (a Plone integration,
CalPlone, is in progress).
 


This example is also interesting, thanks!


--
Lennart Regebro, Nuxeo http://www.nuxeo.com/
CPS Content Management http://www.cps-project.org/
 



___
Zope maillist  -  Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists - 
http://mail.zope.org/mailman/listinfo/zope-announce

http://mail.zope.org/mailman/listinfo/zope-dev )

Re: [Zope] More on understanding conflicts

[Chris McDonough]

On Dec 21, 2005, at 1:07 PM, Dennis Allison wrote:
Sorry if I appeared unresponsive--the fact that we use frames is  
hardly a
secret.   I suppose that it would be helpful to make up soem  
summary of

features for ongoing threads like this one.


It was a secret to me (again, perhaps because of my inability to keep  
a thought in my head for more than an hour, for better or worse) or I  
honestly I wouldn't have asked again.  Just answering the questions  
as they're asked would really, really be the best tact here, because  
configurations change, code changes, and so on.  What was gospel a  
month ago might not be the case now.  So it's important to just  
answer the questions even if it seems utterly redundant to do so.   
Again, I'm not chiding you here, I realize this is hard stuff, but I  
need you to *help me help you* to get this put to bed.



By convention the primary content frame does not cause other frames to
re-render but there are multiple implementors and creaping featurism
which may have changed that.  The navigation_box frame we have been
discussion gets re-rendered on a navigation change (duh) and may  
initiate

re-rendering of a tabs_frame.  Except for the full frameset rendering,
we are likely to be fairly conflict clean.  I can look in the logs and
tell...  Might be interesting.


Yep.. particularly if you see a conflict only in requests that  
directly follow a request for the frameset URL.  If that's the case,  
unless people constantly reload the frameset, you should be OK.


I did not know that XMLHttp interactions were asynchronous but  
serialized.
Most browsers can make multiple simultaneous requests so I'd  
assumed that

XMLHttp would just grab a connection and go and that multiple requests
can be in progress simultaneously.


After going and reading the docs for at least one implementation of  
XMLHttpRequest, I think you're right.  There are some asynchronous  
things going on here.  So I take it back. ;-)



Well, that's good.  Does that mean I'm off the hook? ;-)


Not really off the hook as issues still remain and you are a valuable
resource.  :-)  I need to spend some time thinking about the issues  
an do

some cautious experimentation and testing.


Heh.

- C

___
Zope maillist  -  Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists - 
http://mail.zope.org/mailman/listinfo/zope-announce

http://mail.zope.org/mailman/listinfo/zope-dev )

Re: [Zope] More on understanding conflicts

[Dennis Allison]

Michael -- 

You raise an interesting point.  We use sessions to hold the
volatile state for each user in a highly interactive, highly personalized
site. A session lasts from login until logout or until there has been no
activity for a long time.  Perhaps, if I were to simply excise the session
timeout mechanism and the write of the last access time all would be well.  
We do not use session timeouts and could easily handle the recovery in a 
different way.

I have changed the WRITEGRANULARITY and other parameters to be more 
comensurate with our long session times.

I have begun to think that the Zope session variable mechanism, as
implemented, addresses a different part of the storage spectrum than we
need.  A small number of per user parameters (3 to 10) are used by almost
every request. Most of the parameters are set at user login and are not
changed for the duration of the session; sessions can last a long time, up
to ten hours, say, Some of the parameters change more rapidly, for
example, those that capture the current navigation state.  It may be that
we need two different kinds of session data, one for login-static data and
another for dynamic data.

I'm still working on getting some detailed traceback information,
difficult when the problems occur only infrequently on loaded production
systems with a 24x7 service profile.  We are moving to Zope 2.8.5 to take
advantage of the better conflict reporting.

On Thu, 22 Dec 2005, Michael Dunstan wrote:

 On 12/22/05, Dennis Allison [EMAIL PROTECTED] wrote:
  The issue here has had to do with session variables and their iteraction
  with the persistence mechanism and conflicts and multiple threads for the
  same session.  Chris McDonough has pointed out that session variables can
  cause writes and write conflicts even if the only Zope level access is a
  read.  I thought MVCC works out of the box for Zope 2.8.4 which uses ZODB
  2.3.4. Am I wrong?
 
  The real surprise was that you can get a write conflict from a pair of
  session variable reads!
 
 The missing detail here is that reading a session object causes a
 write to the database to update the last access time for that session
 object. So what looks like a plain old read to the application code
 above, in-fact includes a write just below the surface. (This is a
 design choice so that stale session objects can be removed.)
 
 There are implementation details of TransientObject that attempt to
 mitigate some of the pain:
 
 - The access time has a WRITEGRANULARITY. That can help a bit by
 avoiding writing altogether some of the time. But still there is need
 to write (and so potential contention) each time a boundary of that
 granularity is crossed.
 
 - And _p_resolveConflict of TransientObject will most often pick a
 state to avoid a conflict error. When it does there is the performance
 cost of writing to database but there will be no ConflictError.
 However, I've suggested in the past that you should comment out
 _p_resolveConflict while debugging consistency problems. What is the
 current state of your _p_resolveConflict now? _p_resolveConflict
 includes a DIWM'ly component. Perhaps you still need to avoid that
 component of _p_resolveConflict? In that case a _p_resolveConflict
 could be engineered that can resolve the case of just updates to the
 access time? But still bails out when presented with two states that
 have explicit updates to maintain consistency.
 
 Though that's all just conjecture till we see your tracebacks for your
 conflicts.
 
 michael
 

-- 

___
Zope maillist  -  Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope-dev )

Re: [Zope] More on understanding conflicts

[Chris McDonough]

On Dec 21, 2005, at 2:17 PM, Dennis Allison wrote:

I have begun to think that the Zope session variable mechanism, as
implemented, addresses a different part of the storage spectrum  
than we
need.  A small number of per user parameters (3 to 10) are used by  
almost
every request. Most of the parameters are set at user login and are  
not

changed for the duration of the session;


These would be better implemented as member data (ala CMF's member  
data tool).


- C

___
Zope maillist  -  Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists - 
http://mail.zope.org/mailman/listinfo/zope-announce

http://mail.zope.org/mailman/listinfo/zope-dev )

Re: [Zope] More on understanding conflicts

[Maciej Wisniowski]

The missing detail here is that reading a session object causes a
write to the database to update the last access time for that session
object. So what looks like a plain old read to the application code
above, in-fact includes a write just below the surface. (This is a
design choice so that stale session objects can be removed.)
 


Some time ago (search the archives) I had problems with high rate
of write conflict errors and then Michael Dunstan has written:

One option to reduce the rate of this write conflict is to tune the
session machinery to suit. For example use session-resolution-seconds
of say 300 seconds.

It helped me a lot - almost no conflict errors :) Maybe you should
try to change this setting in zope.conf and see what will happen.

Im curious if there are side effects of setting high value to this
variable? I haven't noticed any...

--
Maciej Wisniowski
___
Zope maillist  -  Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists - 
http://mail.zope.org/mailman/listinfo/zope-announce

http://mail.zope.org/mailman/listinfo/zope-dev )

Re: [Zope] More on understanding conflicts

[Dennis Allison]

The side effect is that sessions will live longer than the specified 
period, up to 300 seconds longer if session-resolution-seconds is set to
30 seconds.

In my case, setting it higher helps, b ut does not eliminate the problems.

On Wed, 21 Dec 2005, Maciej Wisniowski wrote:

 
 The missing detail here is that reading a session object causes a
 write to the database to update the last access time for that session
 object. So what looks like a plain old read to the application code
 above, in-fact includes a write just below the surface. (This is a
 design choice so that stale session objects can be removed.)
   
 
 Some time ago (search the archives) I had problems with high rate
 of write conflict errors and then Michael Dunstan has written:
 
 One option to reduce the rate of this write conflict is to tune the
 session machinery to suit. For example use session-resolution-seconds
 of say 300 seconds.
 
 It helped me a lot - almost no conflict errors :) Maybe you should
 try to change this setting in zope.conf and see what will happen.
 
 Im curious if there are side effects of setting high value to this
 variable? I haven't noticed any...
 
 

-- 

___
Zope maillist  -  Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope-dev )

Re: [Zope] apache open proxy configuration problem

[Ed Colmar]

Hey All..

I'm following up on this thread after lots of different configuration 
attempts, reinstalling apache2 from source, more configuration attempts, 
banging my head against the wall, and endless troubleshooting..  
Unfortuantely I am still failing to configure this correctly.


Thankfully the people using my apache as a open proxy are so relentless 
I only need to start apache for a few seconds to determine if the proxy 
is still open or not...


So...  I've made quite a bit of progress, but I am still at a loss to 
understand what is going on here   Possibly this is a question for 
the apache forum, but I figured some of my fellow zope users might be 
able to help, since all I'm using apache for is to rewrite for zope, and 
log access.


I have cleaned up my virtual host directive to only use a single Rewrite 
Rule (which works):
RewriteRule ^/(.*) 
http://192.168.1.32:8080/VirtualHostBase/http/www.myserver.net:80/myfolder/$1 
[L,P]


Still the proxy was open and under attack.

I turned off mod_proxy and related proxy modules...  But...  The P flag 
in the RewriteRule uses the proxy module though, so the rewrite did not 
work.


I tried removing the P flag, and it does redirect to the appropriate 
page, but does not rewrite the URL correctly.


I have tried using all of the following (inside the virtualhost 
directive, outside of it, and both) to disable the open proxy...  none 
of which have any effect:


Directory proxy:*
Order Deny,Allow
Deny from all
Allow from www.myserver.net
/Directory

ProxyRequests Off

I attempted to use

ProxyBlock *

Which was effective, but also killed the rewrite rule.

Can anyone offer me a decisive way to kill off this open proxy?

I'm getting so frustrated with it I'm considering just ditching apache 
entirely and running zope on port 80.  of course this would mean no 
virtual hosts, but I can live with that in this case.


Please help!

Thanks!

-ed

Kanealii, Priam Mr KRS wrote:


I abandoned mod_proxy for mod_rewrite. Security-wise, mod_rewrite had
less to worry about (this is important when website administration
changes hands).

The sample configuration below shows how to handle Zope resource
quirks and how to proxy requests to and from folders in Zope (both
tested). The last rule is my guess at what proxy everything to and
from Zope would look like (untested). Apache is listening on 80 and
routes requests to a Zope instance listening on 8080.

IfModule mod_rewrite.c

RewriteEngine On
RewriteLog /path/to/rewrite_log

# Zope serves some system-ish content from p_ and misc_.
RewriteRule ^/p_(.*)
http://127.0.0.1:8080/VirtualHostBase/http/%{HTTP_HOST}/VirtualHostRoot/p_$1 
[L,P]
RewriteRule ^/misc_(.*) 
http://127.0.0.1:8080/VirtualHostBase/http/%{HTTP_HOST}/VirtualHostRoot/misc_$1 
[L,P]


# Apache folders served by Zope folders.
RewriteRule ^/folder1(.*) 
http://127.0.0.1:8080/VirtualHostBase/http/%{HTTP_HOST}/VirtualHostRoot/folder1$1 
[L,P]
RewriteRule ^/folder2(.*) 
http://127.0.0.1:8080/VirtualHostBase/http/%{HTTP_HOST}/VirtualHostRoot/folder2$1 
[L,P]


# Push everything to Zope?
RewriteRule ^(.*) 
http://127.0.0.1:8080/VirtualHostBase/http/%{HTTP_HOST}/VirtualHostRoot/$1 
[L,P]


/IfModule

Aloha,
Priam

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf 
Of Ed Colmar

Sent: Saturday, October 15, 2005 9:19 AM
To: zope@zope.org
Subject: [Zope] apache open proxy configuration problem

I've been running zope through apache for years and years now, and I
have a new machine set up with apache 2.0.48 and zope (Zope 2.8.0-final,
python 2.3.5, linux2)

Using Identical Vhost configuration settings from an old machine all has
been well, up until about 5 days ago, when I noticed the machine getting
slammed, and wierd logs started showing up like:

xxx.xxx.xxx.xxx - - [14/Oct/2005:14:09:06 -0700] GET
http://partners.mygeek.com:80/search.jsp?partnerid=98885pagesize=12 
http://partners.mygeek.com:80/search.jsp?partnerid=98885pagesize=12

HTTP/1.1 403 406

(IP removed to protect the guilty)

In my quick research to try to determine the problem, I found people
advising to turn ProxyRequests Off, which I did, but did not have any
effect.

Luckily this is just a development server, not a live production server,
so its not super critical, but I'm nervous now that my production server
might be in the same state...

Here is a sample vhost.conf entry:

NameVirtualHost 192.168.1.32
VirtualHost 192.168.1.32
ServerName www.greengraphics.net
ServerPath /var/www/greengraphics/www
DocumentRoot /var/www/greengraphics/www
ServerAdmin webmaster
RewriteEngine On
TransferLog logs/Vhost-greengraphics-access.log
ProxyRequests Off
Proxy *
Order deny,allow
Allow from all
/Proxy
ProxyPass /
http://192.168.1.32:8080/VirtualHostBase/http/www.greengraphics.net:80/greengraphics/VirtualHostRoot/ 


ProxyPassReverse /

Re: [Zope] apache open proxy configuration problem

[Jens Vagelpohl]

On 21 Dec 2005, at 23:09, Ed Colmar wrote:


Hey All..

I'm following up on this thread after lots of different  
configuration attempts, reinstalling apache2 from source, more  
configuration attempts, banging my head against the wall, and  
endless troubleshooting..  Unfortuantely I am still failing to  
configure this correctly.


Don't get me wrong, but have you ever tried a forum where people  
*really* know Apache well, like a Apache forum? Yes, most of us use  
it in some way, but few are experts. Real Apache gurus will probably  
be able to pinpoint your particular problem better.


jens

___
Zope maillist  -  Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists - 
http://mail.zope.org/mailman/listinfo/zope-announce

http://mail.zope.org/mailman/listinfo/zope-dev )

Re: [Zope] apache open proxy configuration problem

[Tino Wildenhain]

Ed Colmar schrieb:
 Hey All..
 
 I'm following up on this thread after lots of different configuration
 attempts, reinstalling apache2 from source, more configuration attempts,
 banging my head against the wall, and endless troubleshooting.. 
 Unfortuantely I am still failing to configure this correctly.
 
 Thankfully the people using my apache as a open proxy are so relentless
 I only need to start apache for a few seconds to determine if the proxy
 is still open or not...
 
 So...  I've made quite a bit of progress, but I am still at a loss to
 understand what is going on here   Possibly this is a question for
 the apache forum, but I figured some of my fellow zope users might be
 able to help, since all I'm using apache for is to rewrite for zope, and
 log access.
 
 I have cleaned up my virtual host directive to only use a single Rewrite
 Rule (which works):
 RewriteRule ^/(.*)
 http://192.168.1.32:8080/VirtualHostBase/http/www.myserver.net:80/myfolder/$1
 [L,P]
 
 Still the proxy was open and under attack.
 

I'm wondering where you get the impression you have an open proxy?
Given your configuration, no access can go outside your zope.

Sure people will try it all the time - but your apache still
delivers just your zope content.

Just try it out yourself!

___
Zope maillist  -  Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope-dev )

[Zope] [ANN] jsonserver 1.1.pre2 released (AJAX)

[Balazs Ree]

Jsonserver provides an alternative way of AJAX client-server
communication on Zope.

Jsonserver enables Zope to act as a JSON-RPC server. JSON-RPC is
an XML-RPC replacement. It is built on JSON, a javascript based
data interchange format. JSON has bindings for more languages. On
the client side, the jsolait javascript library contains both
JSON and JSON-RPC support, besides other utilities.

Characteristics of this approach are:

- You can bind methods in javascript to Zope methods, python
  scripts or page templates and call them up directly from
  javascript in a synchronous or asynchronous way (RPC).

- Both the call parameters and the return value can be strings,
  unicode strings, instances of any other builtin python data
  type, or structures built with the combination of tuples, lists
  and dicts. These get marshalled transparently with JSON.

- As a consequence there is no necessity to use XML to pass
  around structured data, you can just structure your data with
  python and pass it directly (but of course you also have the
  possibility to pass around XML).
  
- Passing of both positional and keyword parameters allows to
  call up page templates with request parameters.

- Full client compatibility with the Zope3 version of jsonserver,
  i.e.  the same client code will be able to run on Zope2 and
  Zope3 without a change.

This version, 1.1.pre2 is a pre-release and considered to be
beta. It works pretty well but there are things that might need
to change before the final release.

It can be installed on Zope 2.7 and 2.8 (for 2.7 you need to
install Five). It is compatible with Plone and can be used from
it without restrictions.

More information, a simple demo product and download at
http://www.zope.org/Members/ree/jsonserver2 . Please report bugs
directly to me.

-- 
Balazs Ree, email: ree at ree.hu

___
Zope maillist  -  Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope-dev )