Re: [Zope-dev] Re: zope2 requests VS zope3 requests

2006-06-07 Thread Philipp von Weitershausen
Stefan H. Holek wrote: -1 The whole point of sticking with Zope2 is backward compatibility, isn't it? If I wanted something that doesn't run my old products and applications anymore I would go to Zope3 directly, why thank you. Hey, the idea isn't to run Zope 3 directly but to evolve,

Re: [Zope-dev] Re: zope2 requests VS zope3 requests

2006-06-02 Thread Stefan H. Holek
-1 The whole point of sticking with Zope2 is backward compatibility, isn't it? If I wanted something that doesn't run my old products and applications anymore I would go to Zope3 directly, why thank you. Please keep this in mind in your spree to make Zope2 look like Zope3. Backward

[Zope-dev] Re: zope2 requests VS zope3 requests

2006-05-28 Thread Philipp von Weitershausen
Lennart Regebro wrote: On 5/27/06, Rocky Burt [EMAIL PROTECTED] wrote: I've heard rumours that ultimately the preferred manner of integration of z2 and z3 requests was to replace the z2 ZPublisher with the z3 zope.publisher. Well, that would not necessarily mean that the requests are the

Re: [Zope-dev] Re: zope2 requests VS zope3 requests

2006-05-28 Thread Chris McDonough
On May 28, 2006, at 6:53 AM, Philipp von Weitershausen wrote: Lennart Regebro wrote: On 5/27/06, Rocky Burt [EMAIL PROTECTED] wrote: I've heard rumours that ultimately the preferred manner of integration of z2 and z3 requests was to replace the z2 ZPublisher with the z3 zope.publisher.

Re: [Zope-dev] Re: zope2 requests VS zope3 requests

2006-05-28 Thread Philipp von Weitershausen
Chris McDonough wrote: As said, I think the first step towards unifying the request interfaces would be to deprecate the __getattr__ protocol for request variables. I think we should start with Zope 2.11. I'm sure you know this, but I wanted to point out that doing this will break a lot of