Anthony Jones wrote:
>It is an element of the [Form] collection of a Request.
If you were to give that a single word label what would it be?
I already gave one: element. The only other one I would consider is item**,
but that has special meaning in this case, since the element is an object
with properties .Count, and .Item (Item is the default property).
No let me guess anything that but 'Field' right?
Wrong. See above.
>There is no requirement that it be associated with a field,
which I can easily demonstrate with an XMLHttpRequest object.
Or the Gecko extension LiveHTTPHeaders, for that matter.
Some might call that emulation ;)
I call it constructing a request, which is nothing more than a message.
ASP doesn't care about the client but it does support the
'concept' of a Form which has fields.
I would agree that HTML supports that concept, but not ASP.
How the client may or may not represent it isn't it's business...
The client renders the HTML and creates Requests. So if there is a question
of how the client represents something, that should center on the Response
(which creates the HTML), and not on the Request.
You have it exactly backward. The client creates the request, parts of which
ASP assembles into a Request Object and its Form Collection for exposure to
the script. The ASP script creates a Response message, which usually
contains a status of 200, a content-type of text/html, and a text string
representing an HTML document, among other things. The browser chooses how
to represent that HTML document fragment of the response. There is no
"concept of a form" in that response outside the HTML.
but to say tha ASP doesn't have 'Form field constructs' is odd to
say the least when it clearly exposes a collection of values
(which I would call fields) in property called Form is bit like
saying black is white.
It only looks like a "collection of values" to a VBScripter. Those of us who
write ASP in JScript know the truth: Request.Form is a collection of
objects. Admittedly, that fact alone does not make it any more or any less
like a collection of *fields*. But neither does the fact that ASP names the
collection "Form".
Consider this JScript illustration of your argument:
var black = {Count:1,Item:"black"}
if (black == "black") {
Response.Write(black + " is black")
} else {
Response.Write(black + " is white")
}
The output? [object Object] is white.
** I would use item because the JScript Enumerator object exposes them via
..item().
--
Dave Anderson
Unsolicited commercial email will be read at a cost of $500 per message. Use
of this email address implies consent to these terms.
