They should always be available explicitly through a pathVariable() accssor
method. The value() method is meant to provide simple one stop shopping for
your client variable needs. It just goes through the dictionaries, looking
for the requested key, and once it finds it, it bails and returns the first
value it finds. So the question there is, what order should the
dictionaries be searched in?
One answer is to provide a way to change this dynamically. Perhaps maintain
a list of dicts to search, and the user can change the ordering of the dicts
in the list.
Jay
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, August 22, 2001 12:34 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [Webware-devel] Re: Request _pathContext As a
> generalization of Path Session
>
>
> On Wed, Aug 22, 2001 at 12:18:36PM -0400, Clark C . Evans wrote:
> > | - these values can just be merged into the fields along
> with the POST/GET
> > | variables. This would be my preference unless there's
> some compelling
> > | reason they need to be separate. I would make the
> POST/GET values override
> > | the path values if both were present.
> >
> > I think the "values" method would be a better place to
> > make them visible, as I think keeping "fields" with
> > just query parameters is cleaner. The "values"
> > also contains cookie values... which IMHO, makes
> > much more sense, especially considering _SID_ is
> > currently a cookie value. Thus, values can use
> > search order: query-parameters, cookie-values, path-values
>
> 'fields' won't be so pure once we start parsing both GET and
> POST values
> rather than just one or the other. And the same situation will arise:
> whether to offer only merged values (and which to override), or only
> separate values, or both. I say we should offer both, so
> that those who
> want to be lazy can be lazy, and those who want to recognize a value
> only from a certain source can.
>
> --
> -Mike (Iron) Orr, [EMAIL PROTECTED] (if mail problems: [EMAIL PROTECTED])
> http://iron.cx/ English * Esperanto * Russkiy *
> Deutsch * Espan~ol
>
> _______________________________________________
> Webware-devel mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/webware-devel
>
----------------------------------------------------------------------------
This e-mail and any attachments may be confidential or legally privileged.
If you received this message in error or are not the intended recipient, you
should destroy the e-mail message and any attachments or copies, and you are
prohibited from retaining, distributing, disclosing or using any information
contained herein. Please inform us of the erroneous delivery by return
e-mail.
Thank you for your cooperation.
----------------------------------------------------------------------------
_______________________________________________
Webware-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/webware-devel
