Re: [Repoze-dev] Keeping pages out of deliverance's hands

2008-04-13 Thread Chris McDonough
Tom Lazar wrote:
 On Apr 13, 2008, at 6:20 PM, Chris McDonough wrote:
 Tom Lazar wrote:
 On 2008-04-13 01:10:08 +0200, Chris McDonough [EMAIL PROTECTED] said:
 Tom Lazar wrote:
 On 2008-04-12 22:42:22 +0200, Martin Aspeli
 [EMAIL PROTECTED] said:

 Reinout van Rees wrote:
 Hi all,

 One thing that's not clear to me: how to keep certain pages out of
 deliverance's hands? The zmi pages (/manage, /manage_main, etc.) 
 are the
 ones I'm most interested in at the moment.

 If I tickle my brain I come up with some irc messages and some 
 emails,
 but I'm missing the bigger picture, especially after the latest 
 changes.

 Can someone give me a quick pointer?
 I use a paste composite app where / is a pipeline with deliverance 
 in it
 and /admin is a pipeline with plain repoze. It's not perfect for 
 all use
 cases, but pretty easy to set up.

 I'd like the repoze app to be on /, but have some declarative
 configuration to say e.g.

 deliverance.ignore = /manage/.*
 deliverance.ignore = /foo.*

 i.e. a regular expression based thing where deliverance would be 
 told to
 ignore certain incoming url patterns.
 that sounds like something i'd like to have in the webserver config,
 i.e. apache or nginx where i would set some sort of headers (just like
 in the vhm example)

 i'm new to this, but my gut feeling would be to keep all this sort of
 fancy, regex-based rewriting stuff in one place (i.e. the webserver
 config) and to use 'straightforward' tests for defined flags or 
 headers
 within the wsgi pipeline.
 I think the only sane way to do this is to let the application 
 (Plone, or Zope)
 choose the theme on the way out rather than allowing anything to 
 choose the
 theme on the way in, as the regexes will get absolutely crazy if you 
 need to do
 the choosing this way.  IOW, there would be no theme specified in 
 middleware or
 in the webserver config, but Zope would return a header for each 
 response that
 should be themed a certain way.
 sounds good. now which header would that be? or IOW which fine 
 manual[tm] should i read?

 None yet, I don't think the capability exists.
 
 i see. but in the repoze-podcast you (or tres?) alluded to some such 
 functionality being developed in a separate branch, which i've read here 
 on the list somewhere that that has been merged into the trunk. is there 
 any information on that? perhaps even just a revision number with a 
 commit message? any help would be appreciated, thanks.


I *think* this branch was merged back to the trunk:

http://codespeak.net/svn/z3/deliverance/branches/urienv/

But if I'm not mistaken it's something that requires that an envvar be set 
during ingress rather than egress for the middleware to know.

- C


 


 - C


 

___
Repoze-dev mailing list
Repoze-dev@lists.repoze.org
http://lists.repoze.org/listinfo/repoze-dev


Re: [Repoze-dev] Keeping pages out of deliverance's hands

2008-04-12 Thread Paul Everitt
Tom Lazar wrote:
 On 2008-03-12 14:58:14 +0100, Tres Seaver 
 [EMAIL PROTECTED] said:
 
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 Reinout van Rees wrote:
 Paul Everitt schreef:
 Tres made a urienv branch for Deliverance that allows you to put a
 middleware step in front of Deliverance to control which theme gets set.
 That is the one that is now merged back to trunk, right?
 Yes.

 However, what you want is simpler: you can write a middleware step that
 sets the notheme flag on the query string.
 Hey, neat. Didn't know that one :-) Works like a charm in the browser at
 least.


 For making a middleware step: does anyone know a paster skeleton for
 that? Googling for paster skeletons for creating stuff that is to be
 used by paster is a bit hard :-)
 Nope, we've just started for existing examples.
 
 does anybody have a working example of this? i would a) need the 
 functionality and b) it sounds like an excellent starting point to 
 write simple middleware.

Does this == paster skeletons, or the Deliverance keep-your-hands-off 
thing?

-Paul
___
Repoze-dev mailing list
Repoze-dev@lists.repoze.org
http://lists.repoze.org/listinfo/repoze-dev


Re: [Repoze-dev] Keeping pages out of deliverance's hands

2008-04-12 Thread Martin Aspeli
Reinout van Rees wrote:
 Hi all,
 
 One thing that's not clear to me: how to keep certain pages out of 
 deliverance's hands? The zmi pages (/manage, /manage_main, etc.) are the 
 ones I'm most interested in at the moment.
 
 If I tickle my brain I come up with some irc messages and some emails, 
 but I'm missing the bigger picture, especially after the latest changes.
 
 Can someone give me a quick pointer?

I use a paste composite app where / is a pipeline with deliverance in it 
and /admin is a pipeline with plain repoze. It's not perfect for all use 
cases, but pretty easy to set up.

I'd like the repoze app to be on /, but have some declarative 
configuration to say e.g.

deliverance.ignore = /manage/.*
deliverance.ignore = /foo.*

i.e. a regular expression based thing where deliverance would be told to 
ignore certain incoming url patterns.

Martin

-- 
Author of `Professional Plone Development`, a book for developers who
want to work with Plone. See http://martinaspeli.net/plone-book

___
Repoze-dev mailing list
Repoze-dev@lists.repoze.org
http://lists.repoze.org/listinfo/repoze-dev


Re: [Repoze-dev] Keeping pages out of deliverance's hands

2008-04-12 Thread Tom Lazar
On 2008-04-12 22:29:04 +0200, Paul Everitt 
[EMAIL PROTECTED] said:

 Tom Lazar wrote:
 On 2008-03-12 14:58:14 +0100, Tres Seaver
 [EMAIL PROTECTED] said:
 
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1
 
 Reinout van Rees wrote:
 Paul Everitt schreef:
 Tres made a urienv branch for Deliverance that allows you to put a
 middleware step in front of Deliverance to control which theme gets set.
 That is the one that is now merged back to trunk, right?
 Yes.
 
 However, what you want is simpler: you can write a middleware step that
 sets the notheme flag on the query string.
 Hey, neat. Didn't know that one :-) Works like a charm in the browser at
 least.
 
 
 For making a middleware step: does anyone know a paster skeleton for
 that? Googling for paster skeletons for creating stuff that is to be
 used by paster is a bit hard :-)
 Nope, we've just started for existing examples.
 
 does anybody have a working example of this? i would a) need the
 functionality and b) it sounds like an excellent starting point to
 write simple middleware.
 
 Does this == paster skeletons, or the Deliverance keep-your-hands-off
 thing?

ah, good question (as i now realize)

i meant the keep-your-hands-off thing[tm] ;-)

thanks for asking,

tom

 
 -Paul


-- 
Tom Lazar
http://tomster.org


___
Repoze-dev mailing list
Repoze-dev@lists.repoze.org
http://lists.repoze.org/listinfo/repoze-dev