Re: [Zope-dev] Re: z3 server+publication refactor for z2

2006-04-18 Thread Lennart Regebro
FYI there was a couple of hours work done on this today at the sprint in Paris.

It seemed to us the the next necessary step in Sidneis branch was to
make Zope2 traversal adapters for non-zope3 objects. This work has now
started, in the form of refactoring the BaseRequest traversal into
Zope3 type traversal chunks that we can make adapters of.

Current problem: getRole is called with the entry_name unless the
subobject was gotten via a getitem interface, when it's called with
None. As we want to do the getRole part outside of the name traversal,
we don't know in which way the name was gotten. So we need to solve
that tomorrow somehow.

You can check the current status work at
http://svn.zope.org/Zope/branches/easter-sprint_traversal-refactor/
___
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: z3 server+publication refactor for z2

2006-04-13 Thread Andreas Jung



--On 13. April 2006 15:39:06 +0200 Philipp von Weitershausen 
[EMAIL PROTECTED] wrote:

This is the small solution in which we provide a WSGI-capable frontend
to the ZPublisher. The big solution would be to replace ZPublisher
with zope.publisher and a custom Zope2-oriented publication +
appropriate traversers. In this case I wouldn't advise for adapting the
Zope 3 request to a Zope 2 request. I would rather introduce a new
request type, IZope2Request, based on zope.publisher's IBrowserRequest,
that provides all the additional Zope 2 API.

I think the big solution would take a considerable effort. It's less
than three weeks before feature freeze. That is very little time even
for the small solution.



Big or small? Would this be an optional and configurable feature or 
replacement of the current infrastructure?


Andreas


--
ZOPYX Ltd.  Co. KG - Charlottenstr. 37/1 - 72070 Tübingen - Germany
Web: www.zopyx.com - Email: [EMAIL PROTECTED] - Phone +49 - 7071 - 793376
E-Publishing, Python, Zope  Plone development, Consulting


pgpe6PAKRkeFX.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: z3 server+publication refactor for z2

2006-04-13 Thread Andreas Jung

From: Andreas Jung [EMAIL PROTECTED]
To: Philipp von Weitershausen [EMAIL PROTECTED],
Sidnei da Silva [EMAIL PROTECTED], Andreas Jung 
[EMAIL PROTECTED], Florent Guillaume [EMAIL PROTECTED]

cc: List Zope-dev zope-dev@zope.org
Subject: Re: z3 server+publication refactor for z2
Date-Sent: 13. April 2006 15:56:17



--On 13. April 2006 15:53:33 +0200 Philipp von Weitershausen 
[EMAIL PROTECTED] wrote:



Philipp von Weitershausen wrote:

I think the big solution would take a considerable effort. It's less
than three weeks before feature freeze. That is very little time even
for the small solution.


Actually, I *think* I was wrong. The feature freeze will be June 1st,
not May 1st. Perhaps the release manager can clear that up?



Bad question :-) I thought for this yr: 1.7 and 1.12 for the releases
(freeze one month earlier) and starting next yr: 1.6 and 1.12...but can find
find Jim's posting anymore.

-aj


pgpOy7lSAVqU4.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: z3 server+publication refactor for z2

2006-04-13 Thread Andreas Jung



--On 13. April 2006 15:58:44 +0200 Philipp von Weitershausen 
[EMAIL PROTECTED] wrote:

I think the big solution would take a considerable effort. It's less
than three weeks before feature freeze. That is very little time even
for the small solution.


Big or small? Would this be an optional and configurable feature or
replacement of the current infrastructure?


I think it'd be technically possible to have both solutions coexist.
After all, that's what we're doing in Zope 3. zope.app.twisted and
zope.app.server can coexist easily, I don't see why it shouldn't be
possible in Zope 2.


They must coexist in any case. We can not get rid or replace a major
component - neither without breaking compatibility nor without deprecation.

-aj




--
ZOPYX Ltd.  Co. KG - Charlottenstr. 37/1 - 72070 Tübingen - Germany
Web: www.zopyx.com - Email: [EMAIL PROTECTED] - Phone +49 - 7071 - 793376
E-Publishing, Python, Zope  Plone development, Consulting


pgpuHLbQm0kve.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: z3 server+publication refactor for z2

2006-04-13 Thread Andreas Jung



--On 13. April 2006 11:38:38 -0400 Tres Seaver [EMAIL PROTECTED] 
wrote:



-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Florent Guillaume wrote:

Hi,

Sidnei has been working on the Zope 2 publication-refactor branch  where
he's allowed the use of the Zope 3 Twisted-based server, and of  a Zope
3 based publication process.

I'd like to see this merge branched in Zope 2 trunk because I'd like
Zope 2.10 to be Twisted-based. What's missing from the branch
preventing this? What problems have been encountered?


- -1 to using Twisted by default in 2.10 -- it is still much slower than
ZServer, AFAIK.  I don't think we have time to land this and get it
tested before 2.10, frankely, although I wouldn't mind it, assuming that
one had to explicitly configure the server to use Twisted.



Twisted as default really is not acceptable. If it is stable and does not 
inter with the rest of Zope we could include but it really depends on the 
stability and compatibility. Including it just for the sake having it in is 
not acceptable.


-aj

--
ZOPYX Ltd.  Co. KG - Charlottenstr. 37/1 - 72070 Tübingen - Germany
Web: www.zopyx.com - Email: [EMAIL PROTECTED] - Phone +49 - 7071 - 793376
E-Publishing, Python, Zope  Plone development, Consulting


pgp1wThnLyVUS.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 )