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
