[Zope-Checkins] SVN: Zope/trunk/lib/python/DateTime/interfaces.py some minor reshifting
Log message for revision 40388: some minor reshifting Changed: U Zope/trunk/lib/python/DateTime/interfaces.py -=- Modified: Zope/trunk/lib/python/DateTime/interfaces.py === --- Zope/trunk/lib/python/DateTime/interfaces.py2005-11-28 14:49:38 UTC (rev 40387) +++ Zope/trunk/lib/python/DateTime/interfaces.py2005-11-28 14:53:55 UTC (rev 40388) @@ -154,10 +154,6 @@ __le__ = lessThanEqualTo -def dayOfYear(): -Return the day of the year, in context of the timezone -representation of the object - # Component access def parts(): @@ -200,6 +196,10 @@ def DayOfWeek(): Compatibility: see Day +def dayOfYear(): +Return the day of the year, in context of the timezone +representation of the object + def aDay(): Return the abreviated name of the day of the week @@ -348,7 +348,7 @@ A DateTime may be added to a number and a number may be added to a DateTime; two DateTimes cannot be added. -__radd__=__add__ +__radd__ = __add__ def __sub__(other): Either a DateTime or a number may be subtracted from a ___ Zope-Checkins maillist - Zope-Checkins@zope.org http://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/branches/2.9/lib/python/OFS/ Use ObjectCopiedEvent with an 'original' parameter.
Log message for revision 40389:
Use ObjectCopiedEvent with an 'original' parameter.
Changed:
U Zope/branches/2.9/lib/python/OFS/CopySupport.py
U Zope/branches/2.9/lib/python/OFS/ObjectManager.py
U Zope/branches/2.9/lib/python/OFS/OrderSupport.py
-=-
Modified: Zope/branches/2.9/lib/python/OFS/CopySupport.py
===
--- Zope/branches/2.9/lib/python/OFS/CopySupport.py 2005-11-28 14:53:55 UTC
(rev 40388)
+++ Zope/branches/2.9/lib/python/OFS/CopySupport.py 2005-11-28 15:28:49 UTC
(rev 40389)
@@ -33,7 +33,6 @@
from zope.event import notify
from zope.app.event.objectevent import ObjectCopiedEvent
from zope.app.container.contained import ObjectMovedEvent
-import Products.Five # BBB: until Zope 3.2 = r40368 is stiched in
from zope.app.container.contained import notifyContainerModified
from OFS.event import ObjectWillBeMovedEvent
from OFS.event import ObjectClonedEvent
@@ -214,9 +213,10 @@
id = self._get_id(orig_id)
result.append({'id': orig_id, 'new_id': id})
+orig_ob = ob
ob = ob._getCopy(self)
ob._setId(id)
-notify(ObjectCopiedEvent(ob))
+notify(ObjectCopiedEvent(ob, orig_ob))
self._setObject(id, ob)
ob = self._getOb(id)
@@ -385,9 +385,10 @@
message=sys.exc_info()[1],
action='manage_main')
+orig_ob = ob
ob = ob._getCopy(self)
ob._setId(id)
-notify(ObjectCopiedEvent(ob))
+notify(ObjectCopiedEvent(ob, orig_ob))
self._setObject(id, ob)
ob = self._getOb(id)
Modified: Zope/branches/2.9/lib/python/OFS/ObjectManager.py
===
--- Zope/branches/2.9/lib/python/OFS/ObjectManager.py 2005-11-28 14:53:55 UTC
(rev 40388)
+++ Zope/branches/2.9/lib/python/OFS/ObjectManager.py 2005-11-28 15:28:49 UTC
(rev 40389)
@@ -46,7 +46,6 @@
from zope.event import notify
from zope.app.container.contained import ObjectAddedEvent
from zope.app.container.contained import ObjectRemovedEvent
-import Products.Five # BBB: until Zope 3.2 = r40368 is stiched in
from zope.app.container.contained import notifyContainerModified
from OFS.event import ObjectWillBeAddedEvent
from OFS.event import ObjectWillBeRemovedEvent
Modified: Zope/branches/2.9/lib/python/OFS/OrderSupport.py
===
--- Zope/branches/2.9/lib/python/OFS/OrderSupport.py2005-11-28 14:53:55 UTC
(rev 40388)
+++ Zope/branches/2.9/lib/python/OFS/OrderSupport.py2005-11-28 15:28:49 UTC
(rev 40389)
@@ -24,7 +24,6 @@
from DocumentTemplate.sequence import sort
from Globals import InitializeClass
from zope.interface import implements
-import Products.Five # BBB: until Zope 3.2 = r40368 is stiched in
from zope.app.container.contained import notifyContainerModified
from interfaces import IOrderedContainer as z3IOrderedContainer
___
Zope-Checkins maillist - Zope-Checkins@zope.org
http://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/trunk/lib/python/OFS/ Merged 40389 from 2.9 branch:
Log message for revision 40390:
Merged 40389 from 2.9 branch:
Use ObjectCopiedEvent with an 'original' parameter.
Changed:
U Zope/trunk/lib/python/OFS/CopySupport.py
U Zope/trunk/lib/python/OFS/ObjectManager.py
U Zope/trunk/lib/python/OFS/OrderSupport.py
-=-
Modified: Zope/trunk/lib/python/OFS/CopySupport.py
===
--- Zope/trunk/lib/python/OFS/CopySupport.py2005-11-28 15:28:49 UTC (rev
40389)
+++ Zope/trunk/lib/python/OFS/CopySupport.py2005-11-28 15:35:28 UTC (rev
40390)
@@ -37,7 +37,6 @@
from zope.event import notify
from zope.app.event.objectevent import ObjectCopiedEvent
from zope.app.container.contained import ObjectMovedEvent
-import Products.Five # BBB: until Zope 3.2 = r40368 is stiched in
from zope.app.container.contained import notifyContainerModified
from OFS.event import ObjectWillBeMovedEvent
from OFS.event import ObjectClonedEvent
@@ -215,9 +214,10 @@
id = self._get_id(orig_id)
result.append({'id': orig_id, 'new_id': id})
+orig_ob = ob
ob = ob._getCopy(self)
ob._setId(id)
-notify(ObjectCopiedEvent(ob))
+notify(ObjectCopiedEvent(ob, orig_ob))
self._setObject(id, ob)
ob = self._getOb(id)
@@ -390,9 +390,10 @@
message=sys.exc_info()[1],
action='manage_main')
+orig_ob = ob
ob = ob._getCopy(self)
ob._setId(id)
-notify(ObjectCopiedEvent(ob))
+notify(ObjectCopiedEvent(ob, orig_ob))
self._setObject(id, ob)
ob = self._getOb(id)
Modified: Zope/trunk/lib/python/OFS/ObjectManager.py
===
--- Zope/trunk/lib/python/OFS/ObjectManager.py 2005-11-28 15:28:49 UTC (rev
40389)
+++ Zope/trunk/lib/python/OFS/ObjectManager.py 2005-11-28 15:35:28 UTC (rev
40390)
@@ -53,7 +53,6 @@
from zope.event import notify
from zope.app.container.contained import ObjectAddedEvent
from zope.app.container.contained import ObjectRemovedEvent
-import Products.Five # BBB: until Zope 3.2 = r40368 is stiched in
from zope.app.container.contained import notifyContainerModified
from OFS.event import ObjectWillBeAddedEvent
from OFS.event import ObjectWillBeRemovedEvent
Modified: Zope/trunk/lib/python/OFS/OrderSupport.py
===
--- Zope/trunk/lib/python/OFS/OrderSupport.py 2005-11-28 15:28:49 UTC (rev
40389)
+++ Zope/trunk/lib/python/OFS/OrderSupport.py 2005-11-28 15:35:28 UTC (rev
40390)
@@ -24,7 +24,6 @@
from DocumentTemplate.sequence import sort
from Globals import InitializeClass
from zope.interface import implements
-import Products.Five # BBB: until Zope 3.2 = r40368 is stiched in
from zope.app.container.contained import notifyContainerModified
from interfaces import IOrderedContainer as z3IOrderedContainer
___
Zope-Checkins maillist - Zope-Checkins@zope.org
http://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-dev] Re: DateTime mess
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Philipp von Weitershausen wrote: Andrew Milton wrote: -1 for any scheme that involves diddling the ZODB to 'fix' pickles, because you just know you're going to corrupt someone's ZODB, and that's just noone's idea of fun. There are sensible ways of upgrading the ZODB. Zope 3 has had it since 3.0 (called generations) and they've been working reasonably well for these things. They aren't well-enough battle tested to make Andrew's point invalid, I think (there *are* no large ZODB-based Zope3 sites which have undergone generational upgrades). Frankly, anything which attempts to fix pickles in-place smells bad to me. Dump and reload is how the RDBMS world handles this kind of problem, and it isn't because they don't have smart folks working on them. Tres. - -- === Tres Seaver +1 202-558-7113 [EMAIL PROTECTED] Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDiwO++gerLs4ltQ4RAtYdAJ9Y+UDQMou8K7fn/abJiLNkxs7TUwCfauQv woKSNYi9MFGsJKGh+FZGr7c= =929F -END 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] Re: removing test.py from path
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tarek Ziadé wrote: Tarek Ziadé wrote: Hello, Benji recently changed test.py in Z3 in order to avoid collision name with the standard python 'test' module. I bumped into the same problem running tests under Z 2.8. I would like to add this change as well in Z 2.8 bin/test.py if no one objects. Please ensure that 'bin/zopectl test' works from an instance after making your change (at the moment, whoever *last* redid the 2.9 branch / trunk layout left that broken). Tres. - -- === Tres Seaver +1 202-558-7113 [EMAIL PROTECTED] Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDiweq+gerLs4ltQ4RAqjPAKCoyFu4uFOedELnJ6LLVz/opXk1MQCg1EYa XpgcBOwri3kMz5lQZzsZOcs= =j6hc -END 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: removing test.py from path
On 28 Nov 2005, at 13:35, Tres Seaver wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tarek Ziadé wrote: Tarek Ziadé wrote: Hello, Benji recently changed test.py in Z3 in order to avoid collision name with the standard python 'test' module. I bumped into the same problem running tests under Z 2.8. I would like to add this change as well in Z 2.8 bin/test.py if no one objects. Please ensure that 'bin/zopectl test' works from an instance after making your change (at the moment, whoever *last* redid the 2.9 branch / trunk layout left that broken). The reason is that test.py moved from $SOFTWARE_HOME/bin to $SOFTWARE_HOME and zopectl test checks for the old path and then exits. No idea why test.py moved. Similar problem with mkzopeinstance. Moved from bin/ to utilities/. 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: RFC: Reunite Zope 2 and Zope 3 inthe sourcecoderepository
Yes, I know that this is possible. But are you really proposing to start a project like this? Or do you mean Five is going or should go in this direction? It (or Zope 2 development in general, which is becoming indistinguishable from Five) is going in this direction. Just an outsider's naive comment on this: These days all of my plone-based z2 products use z3 interfaces, adapters and views (via Five). I look forward to using more five/z3 functionality everyday (such as events, etc). I'm sure this is still a long way from using pure z3, but with every new version of z2/z3/Five I hope to get closer and closer. - 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 )
[Zope-dev] Folderish or SimpleItem object types for structural content
Hello guys! I have a simple question about the design of hierarchical zope product structures in Zope 2. For example, you have categories, within categories you have sub-categories, within sub-categories you have sub-sub categories, within that you have content items, within content items you haveetcetera. All those products are different 'types', with different functionality and different 'roles' as what they represent, so I write different products for every type. For every object that can contain subobjects you could derive it from 'Folder' (or Object Manager). But when you derive all these product types from 'Folder' you end up with ALOT of objects in your database. In a lot of real world cases you have categories and items, that makes things easy, but what about the structure explained above? My question for you guys is : When do you decide to make it a Folderish object which contains sub-objects, or to make it a Simple Item object with, for example, some structured XML content, or dictionary / list properties containing the 'sub-structure'? The last option is more work, because you have to write your add/edit/delete/etc code yourself, writing it with Folders makes it more easily, but then you have an explosion of objects in the ZODB. I would like to have some fresh thoughts about this, so maybe you can help. Thank you in advance, kind regards, Martijn. -- Martijn Jacobs Four Digits, internet solutions e-mail: [EMAIL PROTECTED] | web: http://www.fourdigits.nl tel: +31 (0)26 44 22 700 | fax: +31 (0)84 22 06 117 ___ 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] Python2.4 Security Audit ETA???
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Aeons ago someone promised that said Zope security audit of Python 2.4 was scheduled for October. I've not yet seen any happy announcements that Zope is now 2.4 compliant, and do want to highlight the importance of achieving this goal. Python2.4 has been out for almost a year now, and it's fairly ubiquitous. There've been many statements made on this list about people quite happily running their Zope's - contrary to white hat advice. With the major distro's, Python is entrenched in their installer and gui processes and *all* packaging is focused around a single python (2.4 for everyone excepting our BastionLinux). In reality it is infeasible to support a second version of Python for Z2. Many modules have SWIG bindings (while core Z2 doesn't require much of this, a number of products do), requiring multiple package versions - build systems cannot cope with this scenario without massive spec customisations (which is all pointless given the window of this requirement - and of course that we've all actually learnt something for python2.5, python2.6 ) We are getting an increasing number of people attempting to load incompatible packages. It is not possible to downgrade python. Most of userland is not competent to get a secondary python2.3 installation running - especially when packages such as python-ldap are simply not available for their old python and new ldap etc etc which all requires custom package builds. We are also stuck in a time-warp actually having to back-port a large proportion of recent linux packages because we'd like to make new features available, increasing costs and testing requirements. It is also no longer possible for customers to subscribe to just a single channel because our core is substantially different to their chosen vendor's installation, and packages will be installed into meaningless python paths etc. Can someone please give me an ETA on this, so I can decide if and how to support zope in light of other pressing linux requirements for our distro. Alan -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.6 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFDi/JXCfroLk4EZpkRAlGgAKC1ZjYut1GG55TlxUyVxtD1y+YLKgCg1IV6 vsT9SOOBMUxBP4i1qo7+7q0= =MuMS -END 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] Python2.4 Security Audit ETA???
Am Dienstag, den 29.11.2005, 17:16 +1100 schrieb Alan Milligan: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, ... With the major distro's, Python is entrenched in their installer and gui processes and *all* packaging is focused around a single python (2.4 for everyone excepting our BastionLinux). Not so true. ... We are getting an increasing number of people attempting to load incompatible packages. It is not possible to downgrade python. Most of userland is not competent to get a secondary python2.3 installation running - especially when packages such as python-ldap are simply not available for their old python and new ldap etc etc which all requires custom package builds. Aha. python2.1-ldap - A LDAP interface module for Python 2.1 python2.2-ldap - A LDAP interface module for Python 2.2 python2.3-ldap - A LDAP interface module for Python 2.3 We are also stuck in a time-warp actually having to back-port a large proportion of recent linux packages because we'd like to make new features available, increasing costs and testing requirements. It is also no longer possible for customers to subscribe to just a single channel because our core is substantially different to their chosen vendor's installation, and packages will be installed into meaningless python paths etc. Can someone please give me an ETA on this, so I can decide if and how to support zope in light of other pressing linux requirements for our distro. Well, while it would certainly fine to have said audit, it isnt really a problem - every since different python versions could happily coexist on every platforms I've seen. Even on win32. But someone has to do it. If you feel the itch - would you help scratching it at least? ++Tino ___ 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] Python2.4 Security Audit ETA???
--On 29. November 2005 17:16:55 +1100 Alan Milligan [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Aeons ago someone promised that said Zope security audit of Python 2.4 was scheduled for October. I've not yet seen any happy announcements that Zope is now 2.4 compliant, and do want to highlight the importance of achieving this goal. I thought the recent postings on this issue were clear enough. Zope 2.9 will *require* Python 2.4.2. The requirements and recommendations for Zope 2.8.X have not changed and are unlikely to change. Please no further discussion about why we still don't support Python 2.4 for Zope 2.8 officially... -aj pgp00frNr9red.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] Re: Zope's Webdav port for RESTful web service
(Sun, Nov 27, 2005 at 12:00:08PM -0500) [EMAIL PROTECTED] wrote/schrieb/egrapse: Am Samstag, den 26.11.2005, 21:17 -0400 schrieb David Pratt: Hi. I am looking at how to implement a RESTful web service in Zope2. Could you expand a bit on whatever a RESTful web service is? Hi Tino, I looked it up in Google. Too me it just looks like a regular buzzword accelerator. You do what you have always done, you just put in a megaton of new acronyms and buzzwords. Instant profit! To the orginal poster: I bet the best way to implement this is by making python scripts and page templates that return xml. No need to mess with webdav. No big deal either. Regards, Sascha ___ 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] how to auto refresh the browser with dtml
how do I do an auto-refresh to my browser with dtml? anyone have any ideas? Yahoo! Music Unlimited - Access over 1 million songs. Try it free.___ 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 auto refresh the browser with dtml
On 28 Nov 2005, at 09:53, Allen Huang wrote: how do I do an auto-refresh to my browser with dtml? anyone have any ideas? Please don't confuse server-side code (like DTML) with browser-side code (like Javascript and HTML). DTML cannot refresh your browser. Use Javascript or HTML. 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] how to auto refresh the browser with dtml
Allen Huang schrieb:
how do I do an auto-refresh to my browser with dtml? anyone have any ideas?
_when_ do you want to refresh?
dtml-call expr=REQUEST.RESPONSE.setHeader('Refresh','10')
or something like that should work. See rfc2616 for headers
and zope-book for API of RESPONSE object.
___
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] DateTime mess
Andreas Jung wrote: I agree that is should be replaced but I also mentioned that we tried to achieve that already some years ago and we gave upso talking about deprecation really makes sense when someone puts a replacement module on the table. I know that the DateTime module is a piece of crap but crap you can live mostly with (as long as you don't need timezones :-)). Okay, well, I'd advocate replacement with a zope.datetime that subclasses python's datetime, mixes in persistence and provides some of the extra helper methods. What do people think? cheers, Chris (CC'ing Phillip 'cos I saw him doing some Zope 3'ish DateTime stuff...) -- 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] DateTime mess
Chris Withers wrote: Andreas Jung wrote: I agree that is should be replaced but I also mentioned that we tried to achieve that already some years ago and we gave upso talking about deprecation really makes sense when someone puts a replacement module on the table. I know that the DateTime module is a piece of crap but crap you can live mostly with (as long as you don't need timezones :-)). Okay, well, I'd advocate replacement with a zope.datetime that subclasses python's datetime, mixes in persistence and provides some of the extra helper methods. What do people think? cheers, Chris (CC'ing Phillip 'cos I saw him doing some Zope 3'ish DateTime stuff...) Hey Chris, hey Hermann, hey others, I've secretly being working on some evil plans to make DateTime more understandable so that we can work out a migration strategy. In my strong opinion, Zope should not maintain its own date/time implementation and I don't even see the need for a zope.datetime like Chris suggests. Why does it need to be persistent? Datetimes are dull values, they should just pickle nicely. If someone needs more than datetime.datetime and pytz, I would be very interested in their usecase... Anyway, my long-term plans are roughly this: 1. Create some extensive tests about how DateTime currently works. I'm currently working on this to see whether any further procedure makes sense. 2. If we find it's possible, we rid the current DateTime implementation and recreate the DateTime class by subclassing datetime.datetime. For backwards compatability, we make sure that old pickles can be revived and that the old DateTime API is supported for two more Zope releases. 3. After two releases we get rid of the old DateTime API and will provide a script to migrate old DateTime pickles to datetime.datetime pickles in the ZODB. I have a proposal for this in works, but you guys made me blurt it out prematurely :). By the way, I only skimmed over this thread, but I haven't actually found anywhere explained what Hermann's problem with strftime was and a detailed suggestion on how his rewrite would take place... Maybe it'd be a good idea to adopt the proposal process we have for Zope 3. Philipp ___ 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] DateTime mess
+---[ Philipp von Weitershausen ]-- | 2. If we find it's possible, we rid the current DateTime implementation | and recreate the DateTime class by subclassing datetime.datetime. For | backwards compatability, we make sure that old pickles can be revived | and that the old DateTime API is supported for two more Zope releases. | | 3. After two releases we get rid of the old DateTime API and will | provide a script to migrate old DateTime pickles to datetime.datetime | pickles in the ZODB. -1 for any scheme that deliberately breaks currently working code / installs. -1 for any scheme that involves diddling the ZODB to 'fix' pickles, because you just know you're going to corrupt someone's ZODB, and that's just noone's idea of fun. Didn't see any mention of fixing ZClasses (not sure if that's an issue). I'm the first in line of the people wanting Zope DateTime to die. However, you need to leave it there. Fix Zope to internally use something different, and provide a new implementation that 'sensible' people can use going forwards. Motivated developers can then move to the new API. Grumbling users can motivate their developers to migrate their code to the new API (or submit patches d8) -- Andrew Milton [EMAIL PROTECTED] ___ 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] DateTime mess
Andrew Milton wrote: +---[ Philipp von Weitershausen ]-- | 2. If we find it's possible, we rid the current DateTime implementation | and recreate the DateTime class by subclassing datetime.datetime. For | backwards compatability, we make sure that old pickles can be revived | and that the old DateTime API is supported for two more Zope releases. | | 3. After two releases we get rid of the old DateTime API and will | provide a script to migrate old DateTime pickles to datetime.datetime | pickles in the ZODB. -1 for any scheme that deliberately breaks currently working code / installs. Agreed. Deprecation is a way of deliberately killing you softly :). Seriously, there's no going forward without getting rid of stuff. Deprecation is a good way of dealing with getting rid of stuff without having currently working code broken instantly. -1 for any scheme that involves diddling the ZODB to 'fix' pickles, because you just know you're going to corrupt someone's ZODB, and that's just noone's idea of fun. There are sensible ways of upgrading the ZODB. Zope 3 has had it since 3.0 (called generations) and they've been working reasonably well for these things. Didn't see any mention of fixing ZClasses (not sure if that's an issue). I'm not sure it is either, but this would be something to be discussed in the proposal discussion process, I guess. But now that you've mentioned it, I will investigate and possibly include notions in the proposal. I'm the first in line of the people wanting Zope DateTime to die. However, you need to leave it there. Fix Zope to internally use something different, and provide a new implementation that 'sensible' people can use going forwards. I don't think that'll work. I've thought about just letting DateTime die and switch to datetime.datetime over completely. However, code that expects Zope to return DateTime-compatible objects would break. I think we need Zope to use some frankendatetime (a datetime.datetime that also supports the old DateTime API) throughout the deprecation period. Whenever people make a call to the old DateTime API on a frankendatetime object, they'll get a deprecation warning telling them to use the datetime.datetime API instead. After the deprecation phase is over, Zope 2 can return pure datetime.datetime objects. By the way, this is really not a thread for zope@zope.org but for [EMAIL PROTECTED] From the beginning, actually. I suggest we move all further discussion there. Philipp ___ 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] DateTime mess
On 11/28/05, Philipp von Weitershausen [EMAIL PROTECTED] wrote: Datetimes are dull values, they should just pickle nicely. They do. A module with extra utilities + timezone support would be nice. 1. Create some extensive tests about how DateTime currently works. I'm currently working on this to see whether any further procedure makes sense. I'm not worried about how it works now. DateTime is buggy and it's behaviour has undergone several subtle changes, sometimes for the worse, without much screaming. :-) 2. If we find it's possible, we rid the current DateTime implementation and recreate the DateTime class by subclassing datetime.datetime. For backwards compatability, we make sure that old pickles can be revived and that the old DateTime API is supported for two more Zope releases. Yeah, it's that pickling revival that worries me. It's non-trivial. -- 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 )
[Zope] why will FastCGI not be supported in the Future.
Hi, I'm a little bit puzzled why there are growing Number of Mails telling that the support for FastCGI will disappear in the future. Why is this. I am running multiple sites that are hybrides of apache/php and zope. It's very easy to set up such a config with mod fastcgi and Apache. It works just fine and very stable, even on heavy load. The posibility to Easy integrate Zope in existing apache/php server was one of our main reasons to use Zope. I know there is a way to do just the same with mod_proxy, but mod_proxy does open new connection for every request while fastcgi uses the same connection for all requests. The is no problem on low load. But with growing load, this can become a Problem. Bye Estartu Gerhard Schmidt| Nick : estartu IRC : Estartu | Fischbachweg 3 || PGP Public Key 86856 Hiltenfingen | EMail: [EMAIL PROTECTED] | on request Germany|| pgp5ZKaBEW8g5.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] why will FastCGI not be supported in the Future.
--On 28. November 2005 13:28:19 +0100 Gerhard Schmidt [EMAIL PROTECTED] wrote: Hi, I'm a little bit puzzled why there are growing Number of Mails telling that the support for FastCGI will disappear in the future. Why is this. I am running multiple sites that are hybrides of apache/php and zope. It's very easy to set up such a config with mod fastcgi and Apache. It works just fine and very stable, even on heavy load. The posibility to Easy integrate Zope in existing apache/php server was one of our main reasons to use Zope. This is not the recommended solution (at least not since several years). There are no plans to remove FastCGI but it is no longer recommended and supported. But this reminds me that we could officially deprecated it and remove it safely after two release cycles (Zope 2.11). -aj pgp7DIkg6Co2l.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] why will FastCGI not be supported in the Future.
On 28 Nov 2005, at 12:28, Gerhard Schmidt wrote: I know there is a way to do just the same with mod_proxy, but mod_proxy does open new connection for every request while fastcgi uses the same connection for all requests. The is no problem on low load. But with growing load, this can become a Problem. Well, it's not a way to do it, it's *the* way. I highly doubt that your assertion about using more connections than just one is a problem, under any circumstance. All very large production sites that I ever dealt with use mod_rewrite/mod_proxy. It simply is not a problem. Or do you have proof? 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] DateTime mess
Lennart Regebro wrote: Datetimes are dull values, they should just pickle nicely. They do. Yes, that's my point. That's why we don't need added persistency. A module with extra utilities + timezone support would be nice. pytz provides some extensive timezone support. Not sure what the extra utilities are, but I don't have a lot of complicated datetime use cases so I could be missing stuff here. 1. Create some extensive tests about how DateTime currently works. I'm currently working on this to see whether any further procedure makes sense. I'm not worried about how it works now. DateTime is buggy and it's behaviour has undergone several subtle changes, sometimes for the worse, without much screaming. :-) Well, I'm not so worried about the past but about the future. I'm currently diving into the matter by writing doctests. If we find that DateTime and datetime.datetime are semantically incompatible, we'll have to think up a different strategy. We'll see :). 2. If we find it's possible, we rid the current DateTime implementation and recreate the DateTime class by subclassing datetime.datetime. For backwards compatability, we make sure that old pickles can be revived and that the old DateTime API is supported for two more Zope releases. Yeah, it's that pickling revival that worries me. It's non-trivial. I agree. Philipp ___ 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] why will FastCGI not be supported in the Future.
On Mon, Nov 28, 2005 at 12:43:44PM +, Jens Vagelpohl wrote: On 28 Nov 2005, at 12:28, Gerhard Schmidt wrote: I know there is a way to do just the same with mod_proxy, but mod_proxy does open new connection for every request while fastcgi uses the same connection for all requests. The is no problem on low load. But with growing load, this can become a Problem. Well, it's not a way to do it, it's *the* way. Thats a real good argument. There is no *the* way. Every situation is different and having as mutch possibilities as possible is allways the best way to do it. I highly doubt that your assertion about using more connections than just one is a problem, under any circumstance. All very large production sites that I ever dealt with use mod_rewrite/mod_proxy. It simply is not a problem. Or do you have proof? Im runnig a very large site with 4 users and a peak arround 60 Requests per second. Having to call connect end all the routines that come with it is quite an increased load. Why. FastCGI work perfectly and efficiently. Thats exactly the usecase Fastcgi was developed for. In none of the Postings is an reason why FastCGI ist bad and therefore not supported in the future. Just to say so it is is not an Answer. So my question is still there. Bye Estartu Gerhard Schmidt| Nick : estartu IRC : Estartu | Fischbachweg 3 || PGP Public Key 86856 Hiltenfingen | EMail: [EMAIL PROTECTED] | on request Germany|| pgp4uCwucIzhm.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] why will FastCGI not be supported in the Future.
On 28 Nov 2005, at 13:05, Gerhard Schmidt wrote: On Mon, Nov 28, 2005 at 12:43:44PM +, Jens Vagelpohl wrote: On 28 Nov 2005, at 12:28, Gerhard Schmidt wrote: I know there is a way to do just the same with mod_proxy, but mod_proxy does open new connection for every request while fastcgi uses the same connection for all requests. The is no problem on low load. But with growing load, this can become a Problem. Well, it's not a way to do it, it's *the* way. Thats a real good argument. There is no *the* way. Every situation is different and having as mutch possibilities as possible is allways the best way to do it. It's a matter of resources, plain and simple. No one has stepped forward to support it, so it atrophied. If you think it's a great thing to keep, volunteer. 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] why will FastCGI not be supported in the Future.
On Mon, Nov 28, 2005 at 01:07:49PM +, Jens Vagelpohl wrote: On 28 Nov 2005, at 13:05, Gerhard Schmidt wrote: On Mon, Nov 28, 2005 at 12:43:44PM +, Jens Vagelpohl wrote: On 28 Nov 2005, at 12:28, Gerhard Schmidt wrote: I know there is a way to do just the same with mod_proxy, but mod_proxy does open new connection for every request while fastcgi uses the same connection for all requests. The is no problem on low load. But with growing load, this can become a Problem. Well, it's not a way to do it, it's *the* way. Thats a real good argument. There is no *the* way. Every situation is different and having as mutch possibilities as possible is allways the best way to do it. It's a matter of resources, plain and simple. No one has stepped forward to support it, so it atrophied. If you think it's a great thing to keep, volunteer. I would if I had the time and the knowlege. But I don't see a Problem with the Code right now. As I said i runs here perfectly smooth. Bye Estartu Gerhard Schmidt| Nick : estartu IRC : Estartu | Fischbachweg 3 || PGP Public Key 86856 Hiltenfingen | EMail: [EMAIL PROTECTED] | on request Germany|| pgpTIRPlMin9i.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] why will FastCGI not be supported in the Future.
On 28 Nov 2005, at 13:25, Gerhard Schmidt wrote: It's a matter of resources, plain and simple. No one has stepped forward to support it, so it atrophied. If you think it's a great thing to keep, volunteer. I would if I had the time and the knowlege. But I don't see a Problem with the Code right now. As I said i runs here perfectly smooth. It works and is supported are two different things. Is supported also means there are people who will come forward and help out when the code breaks or when people ask questions about it. As you have seen yourself, no one does. The answer is (and will remain, unless someone volunteers): Use at your own peril. 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 )
[Zope] Re: Zope's Webdav port for RESTful web service
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 David Pratt wrote: Hi Tino. Here are a couple of links that describe it. Boils down to using regular GET, POST, PUT, and DELETE over HTTP using specific URI's to invoke actions - sort of like XMLRPC over HTTP. It occurred to me that perhaps the current webdav server could be modified to handle requests for this purpose. I wondered how sensible this would be and whether anyone else has considered this or other options for setting up another listener for this type of service to their sites. REST Web Service Conventions: - Plain XML is the data representation format. That isn't part of REST at all. RESTified applications can be built using *any* fileish representation. - HTTP is the transfer protocol. - HTTP's GET, POST, PUT, and DELETE are the access/manipulation verbs. Zope already supports applicatoins built around the standard HTTP verbs. The trickiest thing about REST from Zope's point of view is that its proponents seem to think POST (which is a general purpose verb) should only be used for resource creation. Zope is happy to map POST / GET requests onto *any* publishable method, which means that you have to try hard to abide by the RESTriction. Zope also supports using PUT for resource creation, which the REST folks don't seem to get. - URIs point to individual data records (such as catalog items or customer info). Already doable, and in fact done in many Zope applications. - HTTP authentication and SSL provide security. Likewise. Basically, Zope already provides everything you need, and more (not using the more is the hard part). Tres. - -- === Tres Seaver +1 202-558-7113 [EMAIL PROTECTED] Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDiwV/+gerLs4ltQ4RAjavAJ9PnKZ8rhVi9ZsyCIbrH02tNjzamgCgrsLL iY2u2jHWvH5uT3riUtK+coQ= =B+lA -END 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] why will FastCGI not be supported in the Future.
(Mon, Nov 28, 2005 at 08:28:56AM -0500) [EMAIL PROTECTED] wrote/schrieb/egrapse: From: Gerhard Schmidt [EMAIL PROTECTED] I'm a little bit puzzled why there are growing Number of Mails telling that the support for FastCGI will disappear in the future. Why is this. I am running multiple sites that are hybrides of apache/php and zope. It's very easy to set up such a config with mod fastcgi and Apache. Our perception of reality seems to differ a lot. Setting up hybrid sites with RewriteRules / mod_rewrite and VHM in Zope is incredible easy, much easier than configuring fastCGI in httpd.conf. (And I'm not even counting having to compile fastcgi and hooking it into apache.) In helping relative newbies (to zope|apache) to configure their zope gehind apache setup on #zope (irc.freenode.net)I found out that life is much easier with 2 rewriterules. You will need rewriterules anyway if you want to force /manage access to https. And afer the rewrite rule witch was running, zope behind apache support on #zope has dwindled down a lot. It works just fine and very stable, even on heavy load. Here my experience differs a lot from yours it seems. The posibility to Easy integrate Zope in existing apache/php server was one of our main reasons to use Zope. I know there is a way to do just the same with mod_proxy, but mod_proxy does open new connection for every request while fastcgi uses the same connection for all requests. The is no problem on low load. But with growing load, this can become a Problem. This is the fun part. Only a couple of weeks ago I grew bored having to restart / reinvestigate / sacrifice dead chicken for our one legacy zope instance that was run through fastcgi. Not really high load on the server, but high load on the admin due to apache? zope? getting stuck somehow. Date: Mon, 28 Nov 2005 14:05:22 +0100 In none of the Postings is an reason why FastCGI ist bad and therefore not supported in the future. Just to say so it is is not an Answer. Experiences may differ, see above. For me it's fastcgi, never again. It likely was great at some point in the past, but there is better stuff now. I value the undisturbed time that I can advance our company codebase too high, I don't want to be interrupted all the time with XY hangs. As someone else mentioned, it's up to you! Regards, Sascha ___ 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] why will FastCGI not be supported in the Future.
Bitte schick das auf die Liste. Ich habe keine Lust solche Diskussionen privat zu führen. Danke, Andreas --On 28. November 2005 14:05:22 +0100 Gerhard Schmidt [EMAIL PROTECTED] wrote: On Mon, Nov 28, 2005 at 12:43:44PM +, Jens Vagelpohl wrote: On 28 Nov 2005, at 12:28, Gerhard Schmidt wrote: I know there is a way to do just the same with mod_proxy, but mod_proxy does open new connection for every request while fastcgi uses the same connection for all requests. The is no problem on low load. But with growing load, this can become a Problem. Well, it's not a way to do it, it's *the* way. Thats a real good argument. There is no *the* way. Every situation is different and having as mutch possibilities as possible is allways the best way to do it. I highly doubt that your assertion about using more connections than just one is a problem, under any circumstance. All very large production sites that I ever dealt with use mod_rewrite/mod_proxy. It simply is not a problem. Or do you have proof? Im runnig a very large site with 4 users and a peak arround 60 Requests per second. Having to call connect end all the routines that come with it is quite an increased load. Why. FastCGI work perfectly and efficiently. Thats exactly the usecase Fastcgi was developed for. In none of the Postings is an reason why FastCGI ist bad and therefore not supported in the future. Just to say so it is is not an Answer. So my question is still there. Bye Estartu - --- Gerhard Schmidt| Nick : estartu IRC : Estartu | Fischbachweg 3 || PGP Public Key 86856 Hiltenfingen | EMail: [EMAIL PROTECTED] | on request Germany|| pgpBlgWqyNx6l.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] Re: Zope's Webdav port for RESTful web service
Hi. Thanks Tres and Sascha for replies. Sascha, I think this is right way to go and will make a product to do this and put the templates into skins. As far as URL's, I was hoping to do something like: http://mydomain.com/folder_to_resource/resource_id but I guess it will be enough to append to the url to trigger the method(s) Iike: http://mydomain.com/folder_to_resource/resource_id/get_resource http://mydomain.com/folder_to_resource/resource_id/modify_resource etc.. I am not using xhtml for my exchange but another xml format. I was originally thinking of using a different port for this which is reason for possible use of webdav port instead of regular port. Regards, David On Monday, November 28, 2005, at 09:26 AM, Tres Seaver wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 David Pratt wrote: Hi Tino. Here are a couple of links that describe it. Boils down to using regular GET, POST, PUT, and DELETE over HTTP using specific URI's to invoke actions - sort of like XMLRPC over HTTP. It occurred to me that perhaps the current webdav server could be modified to handle requests for this purpose. I wondered how sensible this would be and whether anyone else has considered this or other options for setting up another listener for this type of service to their sites. REST Web Service Conventions: - Plain XML is the data representation format. That isn't part of REST at all. RESTified applications can be built using *any* fileish representation. - HTTP is the transfer protocol. - HTTP's GET, POST, PUT, and DELETE are the access/manipulation verbs. Zope already supports applicatoins built around the standard HTTP verbs. The trickiest thing about REST from Zope's point of view is that its proponents seem to think POST (which is a general purpose verb) should only be used for resource creation. Zope is happy to map POST / GET requests onto *any* publishable method, which means that you have to try hard to abide by the RESTriction. Zope also supports using PUT for resource creation, which the REST folks don't seem to get. - URIs point to individual data records (such as catalog items or customer info). Already doable, and in fact done in many Zope applications. - HTTP authentication and SSL provide security. Likewise. Basically, Zope already provides everything you need, and more (not using the more is the hard part). Tres. - -- === Tres Seaver +1 202-558-7113 [EMAIL PROTECTED] Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDiwV/+gerLs4ltQ4RAjavAJ9PnKZ8rhVi9ZsyCIbrH02tNjzamgCgrsLL iY2u2jHWvH5uT3riUtK+coQ= =B+lA -END 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 ) ___ 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] why will FastCGI not be supported in the Future.
--On 28. November 2005 13:28:20 + Jens Vagelpohl [EMAIL PROTECTED] wrote: On 28 Nov 2005, at 13:25, Gerhard Schmidt wrote: It's a matter of resources, plain and simple. No one has stepped forward to support it, so it atrophied. If you think it's a great thing to keep, volunteer. I would if I had the time and the knowlege. But I don't see a Problem with the Code right now. As I said i runs here perfectly smooth. It works and is supported are two different things. Is supported also means there are people who will come forward and help out when the code breaks or when people ask questions about it. As you have seen yourself, no one does. The answer is (and will remain, unless someone volunteers): Use at your own peril. I agree. There should be one supported way to achive a goal. In the past we had at least three methods to run Zope (fortunately we kicked PCGI support in the past). My suggestion is to deprecate FCGI officially in the docs and through a deprecation warning and to kick it at some time (not necessarily after two release cycles). So people can still use but they should know that they are using a deprecated feature...objections? -aj pgp6VbjvePiN5.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] why will FastCGI not be supported in the Future.
On 28 Nov 2005, at 14:23, Andreas Jung wrote: I agree. There should be one supported way to achive a goal. In the past we had at least three methods to run Zope (fortunately we kicked PCGI support in the past). My suggestion is to deprecate FCGI officially in the docs and through a deprecation warning and to kick it at some time (not necessarily after two release cycles). So people can still use but they should know that they are using a deprecated feature...objections? The deprecation warning should point out that mod_rewrite is the common way to achieve this goal and that FastCGI is plain unsupported. 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] why will FastCGI not be supported in the Future.
On Mon, Nov 28, 2005 at 03:23:04PM +0100, Andreas Jung wrote: --On 28. November 2005 13:28:20 + Jens Vagelpohl [EMAIL PROTECTED] wrote: On 28 Nov 2005, at 13:25, Gerhard Schmidt wrote: It's a matter of resources, plain and simple. No one has stepped forward to support it, so it atrophied. If you think it's a great thing to keep, volunteer. I would if I had the time and the knowlege. But I don't see a Problem with the Code right now. As I said i runs here perfectly smooth. It works and is supported are two different things. Is supported also means there are people who will come forward and help out when the code breaks or when people ask questions about it. As you have seen yourself, no one does. The answer is (and will remain, unless someone volunteers): Use at your own peril. I agree. There should be one supported way to achive a goal. In the past we had at least three methods to run Zope (fortunately we kicked PCGI support in the past). My suggestion is to deprecate FCGI officially in the docs and through a deprecation warning and to kick it at some time (not necessarily after two release cycles). So people can still use but they should know that they are using a deprecated feature...objections? Sure I object. Why should perfectly working code be removed. There is no alternativ for heavy loaded sites which need integration of apache and zope. mod_proxy is no alternativ because it raises the load even further. Bye Estartu - Gerhard Schmidt | E-Mail: [EMAIL PROTECTED] TU-München| WWW Online Services | Tel: 089/289-25270| Fax: 089/289-25257| PGP-Publickey auf Anfrage pgpwSrYnShhnN.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] why will FastCGI not be supported in the Future.
On 28 Nov 2005, at 14:52, Gerhard Schmidt wrote: Sure I object. Why should perfectly working code be removed. There is no alternativ for heavy loaded sites which need integration of apache and zope. mod_proxy is no alternativ because it raises the load even further. Sorry, I have to call Bullshit on the assertion that mod_proxy raises the load in any horrible way. I have been using Zope for more than 6 years and no one has ever made this claim or provided proof that this is so. 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] why will FastCGI not be supported in the Future.
--On 28. November 2005 15:52:25 +0100 Gerhard Schmidt [EMAIL PROTECTED] wrote: Sure I object. Why should perfectly working code be removed. There is no alternativ for heavy loaded sites which need integration of apache and zope. mod_proxy is no alternativ because it raises the load even further. I've seen lots of heavy loaded Zope sites - I've not seen a single one using FastCGI. Can you give us some number about the FastCGI performance compared to the standard mod_rewrite approach? Let numbers speakBut please read carefully...I wrote about deprecating the module but not about removing it as in my original posting. We want o make clear that FCGI is not supported. You are of course free to use it as long as you need. -aj pgpxmCqVb51yR.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] Re: Zope's Webdav port for RESTful web service
Yeah, if POST and GET are desired to have semantic differences, your code will have to explicitly check request['REQUEST_METHOD']. On 11/28/05, Tres Seaver [EMAIL PROTECTED] wrote: The trickiest thing about REST from Zope's point of view is that its proponents seem to think POST (which is a general purpose verb) should only be used for resource creation. Zope is happy to map POST / GET requests onto *any* publishable method, which means that you have to try hard to abide by the RESTriction. Zope also supports using PUT for resource creation, which the REST folks don't seem to get. -- http://www.slinkp.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] why will FastCGI not be supported in the Future.
On Mon, Nov 28, 2005 at 04:29:22PM +0100, Gerhard Schmidt wrote: I don't have exakt numbers. We started with pcgi and had heavy problems under load. They disapeared with the fastCGI module coming wird zope 2.6 i gues. I ve tried mod_proxy back than but had many problems. I can not test on the Production system as there are 4 users on the system and we have enougth Problems with Readconflictes and Session problems. I'm not surprised you had problems with PCGI, it was known to be extremely slow. AFAIK it ran zope in single-threaded mode so concurrency was terrible. It sounds like you have concluded that, because FCGI is faster than PCGI, then FCGI must also be faster than mod_rewrite / mod_proxy. That's just not logical. p.s. If you're having session problems and read conflicts with 2.6, you should strongly consider upgrading to *at least* 2.7.3 and maybe 2.8. Heavy use of sessioning is still not perfect (see Dennis Allison's recent threads), but it is *much* better since 2.7.3. In addition, ReadConflictErrors are greatly reduced since the release of ZODB 3.3, which first shipped with Zope 2.8. -- Paul Winkler http://www.slinkp.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 )
[Zope] ZMI
I have had to reinstall Plone and Zope on my computer. I now find that when I try to log into ZMI and http://localhost:8080/manage comes up, it tells me that I am not authorised to view this resource. I am using the correct user name and password. I would be gratefu if anyone could suggest how to resolve this problem. Yours sincerely Mark Smith ___ 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 Foundation draft docs available for review/comment
Hello everyone: We have published a draft set of formation documents for the Zope Foundation. A zip file of the complete set of docs is available online at: o http://tinyurl.com/7crf8 The next steps in the process are: o Community review, comment, incorporate feedback cycle(s) (one or two?) o Submit final drafts to the Software Freedom Law Center (SFLC) for iteration/editing/polishing o Form the Foundation! :^) Please participate in the review and comment period. You can do so via IRC and/or email. o IRC: We have scheduled the following IRCs to discuss the docs in real time: Who: Zope Community What: IRC to discuss Zope Foundation formation documents. Where: #zope on irc.freenode.net When: #1: Fri, Dec 9, 730a - 9a (US/EST) #2: Tue, Dec 20, 730a - 830a (US/EST) US/EST is GMT-5. o Email: We've also created a mailing list for Foundation-related topics. This list is available at: http://mail.zope.org/mailman/listinfo/foundation Please subscribe to this list for email-based discussions of the foundation. We would like to thank the formation review committee for their careful work reading, reviewing and commenting on the drafts up to this point. o Takeshi Yamamoto, CEO, Zope Japan KK o Jan Smith, OzZope o Jean-Marc Orliaguet, Chalmers University/CPSSkins o Kit Blake, CEO, Infrae o Christian Theune, CEO, Gocept and DZUG o Eric Barroca, Managing Partner, Nuxeo o Hadar Pedhazur, Chairman, Zope Corp o Rob Page, CEO, Zope Corp o Rajesh Setty, Chairman, Cignex o Dan Ravicher, Legal Director, Software Freedom Law Center o Karen Sandler, Counsel, Software Freedom Law Center Finally, Kit Blake and Jan Smith have been kind enough to volunteer to work on a FAQ. We will work to get this public in the near future. Special thanks to them - I imagine their FAQ work will increase somewhat for the next couple of weeks. :^) Regards, Rob -- Rob Page V: 540 361 1710 Zope Corporation F: 703 995 0412 ___ 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] Re: Zope's Webdav port for RESTful web service
On 28 Nov 2005 at 8:26, Tres Seaver wrote:
requests onto *any* publishable method, which means that you have to
try hard to abide by the RESTriction. Zope also supports using PUT
for resource creation, which the REST folks don't seem to get.
I'm not sure what part REST folks don't seem to get regarding PUT.
But in any case, I have not been able to get PUT to work in a
PythonScript in Zope 2.7.2 because PythonScript objects have a PUT
method that assumes it's a DAV upload.
PythonScript.py line 368 or so
def PUT(self, REQUEST, RESPONSE):
Handle HTTP PUT requests
self.dav__init(REQUEST, RESPONSE)
self.dav__simpleifhandler(REQUEST, RESPONSE, refresh=1)
self.write(REQUEST.get('BODY', ''))
RESPONSE.setStatus(204)
return RESPONSE
Plus that method is protected by Change Python Scripts permission as
well.
--
Brad Clements,[EMAIL PROTECTED](315)268-1000
http://www.murkworks.com
AOL-IM or SKYPE: BKClements
___
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] xform in zope 2.8
Tim Nash wrote at 2005-11-27 16:16 -0800: ... Does anybody know how to monkey patch 2.8.0 so zope can process an xform? I found the xmlFix patch but a fellow zope user pointed out that 2.8.1 breaks the monkey patch because of the zope.app.publication.HTTPPublicationRequestFactory object. zope.app (and everything below) is Zope3 and not yet actively used in Zope2's ZPublisher. Especially, it should not prevent xform processing by Zope2 (after you fixed its ZPublisher). -- Dieter ___ 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 2.8.4 strange behavior
Paul Winkler wrote at 2005-11-27 21:17 -0500: ... I've seen the same symptoms a number of times recently with zope 2.7.x. In our case, it seems to be related to ZEO. Zope seems to have lost its connection to ZEO but doesn't realize it somehow. My theory is that the symptom starts when all worker threads are waiting for objects that aren't in the ZEO client cache, so they're all waiting on ZEO requests. Do you have a firewall between Zope and ZEO? Usually, the OS can inform both ends of a connection when the connection is torn down. However, some firewalls tear a connection down in a way that the endpoints do not get informed. We had to implement a keep alive mechanism to prevent our firewall from behaving in this nasty way. -- Dieter ___ 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] ZMI
Look at the SECURITY.txt file in your ZOPE/doc folder. There you can find instructions to solve your problem. José Henrique.2005/11/28, Mark Smith [EMAIL PROTECTED]: I have had to reinstall Plone and Zope on my computer.I now find that whenI try to log into ZMI and http://localhost:8080/manage comes up, it tells methat I am not authorised to view this resource.I am using the correct user name and password.I would be gratefu if anyone could suggest how toresolve this problem.Yours sincerelyMark Smith___Zope maillist- Zope@zope.orghttp://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] ZMI
On Mon, 2005-11-28 at 17:08 +, Mark Smith wrote: I am using the correct user name and password. I would be gratefu if anyone could suggest how to resolve this problem. Reinitialize the zope admin password? or just create a zope admin user with: # /path/to/zopectl adduser a_name a_password (Zope must be turned off first, you must have a shell acces to do that) -- A powerfull GroupWare, CMS, CRM, ECM: CPS (Open Source GPL). Opengroupware, SPIP, Plone, PhpBB, JetSpeed... are good: CPS is better. http://www.cps-project.org for downloads documentation. Free hosting of CPS groupware: http://www.objectis.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 )
[Zope] Zope Version
How do I determine which version of Plone/Zope I am using? Is there a version file somewhere in the Zope hierarchy? I can't seem to find one. Any help would be appreciated. Thanks. - Asad ___ 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 Version
Just look in the Management Interface, in the Control Panel ... J.F. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Asad Habib Sent: November 28, 2005 3:54 PM To: zope@zope.org Subject: [Zope] Zope Version How do I determine which version of Plone/Zope I am using? Is there a version file somewhere in the Zope hierarchy? I can't seem to find one. Any help would be appreciated. Thanks. - Asad ___ 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] Zope 2.8.4 strange behavior
On Mon, Nov 28, 2005 at 08:19:23PM +0100, Dieter Maurer wrote: Paul Winkler wrote at 2005-11-27 21:17 -0500: ... I've seen the same symptoms a number of times recently with zope 2.7.x. In our case, it seems to be related to ZEO. Zope seems to have lost its connection to ZEO but doesn't realize it somehow. My theory is that the symptom starts when all worker threads are waiting for objects that aren't in the ZEO client cache, so they're all waiting on ZEO requests. Do you have a firewall between Zope and ZEO? Yes, we do, and it is under control of another part of the company :-( Usually, the OS can inform both ends of a connection when the connection is torn down. However, some firewalls tear a connection down in a way that the endpoints do not get informed. I suspected as much... thanks. We had to implement a keep alive mechanism to prevent our firewall from behaving in this nasty way. OK. Can you give a high-level summary of what you did? I thought of using heartbeat to detect loss of connection, but I'm not sure what I could do on failure short of restarting Zope. -- Paul Winkler http://www.slinkp.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] Zope Version
Hi. I looked in there already but it does not state the version. This is what it says: Zope Version (unreleased version, python 2.3.3, darwin) - Asad On Mon, 28 Nov 2005, Doyon, Jean-Francois wrote: Just look in the Management Interface, in the Control Panel ... J.F. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Asad Habib Sent: November 28, 2005 3:54 PM To: zope@zope.org Subject: [Zope] Zope Version How do I determine which version of Plone/Zope I am using? Is there a version file somewhere in the Zope hierarchy? I can't seem to find one. Any help would be appreciated. Thanks. - Asad ___ 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] Zope Version
Ah yes, some earlier zope 2.7 versions had that problem ... And at some point, python 2.3.4 and then 2.3.5 became the recommended python versions. So you're probably somewhere between 2.7 and 2.7.3 ... 2.7.4 prefers python 2.3.4. You can always do a grep -r 2.7 * from the root of your Zope installation, see if it's in there somewhere? I believe there is a VERSION.txt file, but it probably is the containing the bad version identifier. J.F. -Original Message- From: Asad Habib [mailto:[EMAIL PROTECTED] Sent: November 28, 2005 4:03 PM To: Doyon, Jean-Francois Cc: zope@zope.org Subject: RE: [Zope] Zope Version Hi. I looked in there already but it does not state the version. This is what it says: Zope Version (unreleased version, python 2.3.3, darwin) - Asad On Mon, 28 Nov 2005, Doyon, Jean-Francois wrote: Just look in the Management Interface, in the Control Panel ... J.F. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Asad Habib Sent: November 28, 2005 3:54 PM To: zope@zope.org Subject: [Zope] Zope Version How do I determine which version of Plone/Zope I am using? Is there a version file somewhere in the Zope hierarchy? I can't seem to find one. Any help would be appreciated. Thanks. - Asad ___ 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] Zope Version
You can also look near the top of doc/CHANGES.txt in your zope software tree. -PW On Mon, Nov 28, 2005 at 04:08:03PM -0500, Doyon, Jean-Francois wrote: Ah yes, some earlier zope 2.7 versions had that problem ... And at some point, python 2.3.4 and then 2.3.5 became the recommended python versions. So you're probably somewhere between 2.7 and 2.7.3 ... 2.7.4 prefers python 2.3.4. You can always do a grep -r 2.7 * from the root of your Zope installation, see if it's in there somewhere? I believe there is a VERSION.txt file, but it probably is the containing the bad version identifier. J.F. -Original Message- From: Asad Habib [mailto:[EMAIL PROTECTED] Sent: November 28, 2005 4:03 PM To: Doyon, Jean-Francois Cc: zope@zope.org Subject: RE: [Zope] Zope Version Hi. I looked in there already but it does not state the version. This is what it says: Zope Version (unreleased version, python 2.3.3, darwin) - Asad On Mon, 28 Nov 2005, Doyon, Jean-Francois wrote: Just look in the Management Interface, in the Control Panel ... J.F. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Asad Habib Sent: November 28, 2005 3:54 PM To: zope@zope.org Subject: [Zope] Zope Version How do I determine which version of Plone/Zope I am using? Is there a version file somewhere in the Zope hierarchy? I can't seem to find one. Any help would be appreciated. Thanks. - Asad ___ 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 ) -- Paul Winkler http://www.slinkp.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 )
[Zope] Re: ASP404 on Win2003
On 11/24/05, Brian Sullivan [EMAIL PROTECTED] wrote: I have for a while successfully used the ASP404 script ( http://www.zope.org/Members/hiperlogica/ASP404) front ending part of a zope server using IIS on Win2000. Recently I changed the front end server to Win2003. I have been attempting to use the same technique there. All seems to work except for the fact that the FORM part of the request header appears to go missing during the process-- so all form submits in my particular case fail. I have yet to determine the root cause, but near as I can tell the FORM request segment loss happens before the asp script gets to handle the redirection, presumably a change in Win2003's 404/405 error handling strips this out intentionally or inadvertently? Are others seeing this same phenomenon? Any work around? I figured out what the problem was -- it seems the ASP404 script depends on REQUEST_METHOD set in the request header to decide what mode to open WinHTTP in. On Win2000 the REQUEST_METHOD is set to the method of the request (GET/POST). On 2003 the method is always set to GET regardless of the original method. The only solution I could find was to use Request.totalbytes 0 as a check to set the WinHTTP open mode. Something like: openmode = Request.ServerVariables(REQUEST_METHOD)if Request.totalBytes 0 thenopenmode =POSTend ifzopeServer.Open openmode, zopeRequest, False Somehow it seems like not a very satisfying solution but it serves my purpose at this point. ___ 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 Version
look at doc/CHANGES.txt --On 28. November 2005 15:54:23 -0500 Asad Habib [EMAIL PROTECTED] wrote: How do I determine which version of Plone/Zope I am using? Is there a version file somewhere in the Zope hierarchy? I can't seem to find one. Any help would be appreciated. Thanks. - Asad ___ 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 ) pgpaIqFBxbGw0.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] why will FastCGI not be supported in the Future.
On Mon, Nov 28, 2005 at 11:06:35AM -0500, Paul Winkler wrote: On Mon, Nov 28, 2005 at 04:29:22PM +0100, Gerhard Schmidt wrote: I don't have exakt numbers. We started with pcgi and had heavy problems under load. They disapeared with the fastCGI module coming wird zope 2.6 i gues. I ve tried mod_proxy back than but had many problems. I can not test on the Production system as there are 4 users on the system and we have enougth Problems with Readconflictes and Session problems. I'm not surprised you had problems with PCGI, it was known to be extremely slow. AFAIK it ran zope in single-threaded mode so concurrency was terrible. It sounds like you have concluded that, because FCGI is faster than PCGI, then FCGI must also be faster than mod_rewrite / mod_proxy. That's just not logical. No, I just described the way we came to fastcgi and that it solved some of the Problems back than. I pretty sure that mod_proxy is much better than pcgi was. But logic tells me that it can't be better than fastcgi. Building a new connection costs time and CPU power and as the this connections have to be build for each request the impact grows with the number of requets. p.s. If you're having session problems and read conflicts with 2.6, you should strongly consider upgrading to *at least* 2.7.3 and maybe 2.8. Heavy use of sessioning is still not perfect (see Dennis Allison's recent threads), but it is *much* better since 2.7.3. In addition, ReadConflictErrors are greatly reduced since the release of ZODB 3.3, which first shipped with Zope 2.8. We are running zope 2.7.8 at the moment and working on mirgating to 2.8.x at the moment exaly for this reasons. Bye Estartu Gerhard Schmidt| Nick : estartu IRC : Estartu | Fischbachweg 3 || PGP Public Key 86856 Hiltenfingen | EMail: [EMAIL PROTECTED] | on request Germany|| pgpcTtGXzcgnf.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 )
