Re: [Zope-dev] warning: current SiteAccess (1.0.1) breaks current CVS Zope.
Chris Withers wrote Does that mean 2.2 is going to break SiteAccess?! :(
No, I suspect it means Evan hasn't updated SiteAccess yet. SiteAccess hacks into the request handling and traversal code in a fairly brutal way - the recent changes to traversal and security have no doubt broken this. Anthony
Anthony Baxter wrote:
No, I suspect it means Evan hasn't updated SiteAccess yet. SiteAccess hacks into the request handling and traversal code in a fairly brutal way - the recent changes to traversal and security have no doubt broken this.
Not again! Poor Evan must get fed up with having to recode SiteAccess every release. I wish there was some way we could entice DC to rolling this functionality into the Zope core in a better way. How does the Traversal interface bear on this? Chris
Chris Withers wrote:
Anthony Baxter wrote:
No, I suspect it means Evan hasn't updated SiteAccess yet. SiteAccess hacks into the request handling and traversal code in a fairly brutal way - the recent changes to traversal and security have no doubt broken this.
Not again!
Poor Evan must get fed up with having to recode SiteAccess every release.
I wish there was some way we could entice DC to rolling this functionality into the Zope core in a better way.
That's Evan's plan (he works here at DC now, you know. <g>) Shane
Shane Hathaway wrote:
I wish there was some way we could entice DC to rolling this functionality into the Zope core in a better way.
That's Evan's plan (he works here at DC now, you know. <g>)
Yup, I knew... ;-) Sadly, it doesn't seem to be very high up anyone else's agenda at DC.
From what I understand, DC aren't even officially supporting SiteAccess.
<RANT> All of which sux ;-( Virtual Hosting like this is a really common need and I wish someone would just bite the bullet and do it properly in Zope... </RANT> cheers ;-) Chris
----- Original Message ----- From: Chris Withers <chrisw@nipltd.com>
Poor Evan must get fed up with having to recode SiteAccess every release.
Yep.
I wish there was some way we could entice DC to rolling this functionality into the Zope core in a better way.
How does the Traversal interface bear on this?
Once Jim and I can agree on the details, the fundamental mechanism of SiteAccess (the __before_traverse__ hook) *will* become part of standard Zope. The new Traversal interface will make ZCatalog & Co. play nice with virtual hosting, and we can all get off the treadmill. Believe me, I'm pushing this as hard as I can. Cheers, Evan @ digicool & 4-am
Evan Simpson wrote:
Poor Evan must get fed up with having to recode SiteAccess every release.
Yep.
*grin*
Once Jim and I can agree on the details, the fundamental mechanism of SiteAccess (the __before_traverse__ hook) *will* become part of standard Zope. The new Traversal interface will make ZCatalog & Co. play nice with virtual hosting, and we can all get off the treadmill. Believe me, I'm pushing this as hard as I can.
If there's any more 'pushing' the community can do, let us know :-) My wishlist: A SiteRoot object that only becomes active if the incoming request comes through a given (set of) domain names. Failing that, SiteRoots (and AccessRules!! ;-) that have the same interface as SiteAccess but which work with ALL Zope's URL gadgetry (yes, that includes absolute_url! ;-) My $0.02, Chris
participants (4)
-
Anthony Baxter -
Chris Withers -
Evan Simpson -
Shane Hathaway