[cgiapp] params, params, params...

[Ben Hitz]

I do this but for stuff that is NOT a cgi parameter, like a reference  
to another object.

Ben
On Feb 13, 2008, at 3:29 PM, Mark Knoop wrote:

>>
>> Having said that, I can understand you might want a variable whose  
>> value
>> happens to come from one of several sources. I think such logic would
>> fit in your super class, and be stored in CGI::App's param() cache,
>> rather than inventing another (4th) location for such a cache. That 4
>> alone tells you it's overkill.
>>
>
> Is it bad policy to add properties to the CGI::App itself?
>
> eg saying
>
> $self->{my_special_value} = 'SOME_VALUE';
>
> instead of
>
> $self->param(my_special_value, 'SOME_VALUE');
>
> ?
>
> I guess it is bad policy otherwise the params method would not  
> exist but it would be useful to understand exactly why this is?
>
> Cheers
> Mark
>
> #####  CGI::Application community mailing list  ################
> ##                                                            ##
> ##  To unsubscribe, or change your message delivery options,  ##
> ##  visit:  http://lists.openlib.org/mailman/listinfo/cgiapp    ##
> ##                                                            ##
> ##  Web archive:   http://lists.openlib.org/pipermail/cgiapp/   ##
> ##  Wiki:          http://cgiapp.erlbaum.net/                 ##
> ##                                                            ##
> ################################################################

--
Ben Hitz
Senior Scientific Programmer ** Saccharomyces Genome Database ** GO  
Consortium
Stanford University ** hitz at genome.stanford.edu