Can someone explain to me why the CVS version of Zope2 contains references to BASEPATH and the recently released 2.2.2 doesn't? Is this a new feature? -- Robin Becker
Can someone explain to me why the CVS version of Zope2 contains references to BASEPATH and the recently released 2.2.2 doesn't? Is this a new feature? -- Robin Becker
BASEPATHx (and its converse URLPATHx) are analogous to the current BASEx and URLx variables of the REQUEST object, except that they take any fiddling of the path (such as that done by SiteAccess) into account. They will be introduced in the next feature release (2.3). BASEx and URLx will continue to work, but will be deprecated in favor of the new BASEPATHx and URLPATHx. Hope this helps! Brian Lloyd brian@digicool.com Software Engineer 540.371.6909 Digital Creations http://www.digicool.com
From: Brian Lloyd <brian@digicool.com>
BASEPATHx (and its converse URLPATHx) are analogous to the current BASEx and URLx variables of the REQUEST object, except that they take any fiddling of the path (such as that done by SiteAccess) into account. They will be introduced in the next feature release (2.3). BASEx and URLx will continue to work, but will be deprecated in favor of the new BASEPATHx and URLPATHx.
Whoa there! BASEPATHx and URLPATHx are the path portion of BASEx and URLx respectively. That is, if BASE1 == "http://www.foo.com/x/y/z" then BASEPATH1 == "/x/y/z". All of these take path manipulation into account. It's SCRIPT_NAME, REQUEST.script, and the various surgical contortions which try to extract the path part of URLs that are deprecated by these newcomers. Any place SCRIPT_NAME used to appear, it should be replaced with BASEPATH1. Cheers, Evan @ digicool & 4-am
uh - yes, what Evan said. :^) Brian Lloyd brian@digicool.com Software Engineer 540.371.6909 Digital Creations http://www.digicool.com
-----Original Message----- From: zope-dev-admin@zope.org [mailto:zope-dev-admin@zope.org]On Behalf Of Evan Simpson Sent: Friday, November 03, 2000 10:51 AM To: Brian Lloyd; Robin Becker; zope-dev@zope.org Subject: Re: [Zope-dev] BASEPATH
From: Brian Lloyd <brian@digicool.com>
BASEPATHx (and its converse URLPATHx) are analogous to the current BASEx and URLx variables of the REQUEST object, except that they take any fiddling of the path (such as that done by SiteAccess) into account. They will be introduced in the next feature release (2.3). BASEx and URLx will continue to work, but will be deprecated in favor of the new BASEPATHx and URLPATHx.
Whoa there! BASEPATHx and URLPATHx are the path portion of BASEx and URLx respectively. That is, if BASE1 == "http://www.foo.com/x/y/z" then BASEPATH1 == "/x/y/z". All of these take path manipulation into account.
It's SCRIPT_NAME, REQUEST.script, and the various surgical contortions which try to extract the path part of URLs that are deprecated by these newcomers. Any place SCRIPT_NAME used to appear, it should be replaced with BASEPATH1.
Cheers,
Evan @ digicool & 4-am
_______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
participants (3)
-
Brian Lloyd -
Evan Simpson -
Robin Becker