Re: Other Globals in %once

On Apr 28, 2004, at 4:47 PM, Dave Rolsky wrote:

> Well, first of all, _we_ only have control over the Mason request 
> object
> var (and the Apache request var, too), so this wouldn't really have 
> helped
> with Bricolage, because Mason can't set those for you.

Yes it does, because I use set_global() to tell Mason to set them. So 
it does, but only after the %once block has executed.

> Second, I'm just not sure we should encourage people to use these vars 
> in
> the once section, because it'll just be likely to create problems.  As 
> you
> pointed out, you can already get at the request if you really want.

Yes, so my point is that you're not really avoiding problems by 
disallowing it, but you are preventing folks from, for example, using a 
function component to determine what to assign to a persistent (that 
is, %once block) variable by calling it with $m->comp(). This is a drag 
in low persistence environments such as a single Bricolage burn.

So I return to my original question: What are the downsides to my 
setting up those globals before Mason does? That is, of not using 
set_global()?

Thanks,

David



-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g. 
Take an Oracle 10g class now, and we'll give you the exam FREE. 
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click