On Wed, Aug 22, 2001 at 11:52:48AM -0400, Geoff Talvola wrote:
| I'm ready to apply this patch to Webware CVS, but now I'm wondering if
| "pathContext" is the best choice of a name for these fields. I can think
| of additional possibilities:
|
| - call them "pathFields", "pathValues", or "pathVariables".
Let's call them "pathValues".
| - 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
| Also, the patch doesn't include any accessor methods in HTTPRequest.py to
| actually retrieve the values in self._pathContext. If we just merge them
| into the fields, it's not necessary, but otherwise accessors are
| needed.
Being able to ask for them via "value" is all that
is required for me. You can't really set them without
a re-direct... so read-only "values" access is perfect.
Wonderful!
Clark
_______________________________________________
Webware-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/webware-devel
