Current spec language:
requestParameters: Name/value pairs reflected from the query string of
the activated URL. These are the query string parameters the Consumer did
not consume by processing them itself. Other name value pairs (e.g. HTTP
headers from the client or additional Consumer-supplied data) should be
placed in the extensions array.
This certainly covers the first 2 (action URLs and method=get both use
query strings). We may want to expand it to include the third as well.
Could not a .Net Producer just supply the same values for both APIs?
Rich Thompson
Gil Tayar
<Gil.Tayar@webcol To:
lage.com> cc:
Subject: [wsrp-wsia] [I#179] requestParameter semantics unclear
12/10/2002 03:18
AM
Issue: 179
Status: Active
Topic: interface
Class: Minor_Editorial
Raised by: Eilon Reshef
Title: requestParameter semantics unclear
Date Added: 10-Dec-2002
Document Section: v0.85/5.1.6
Description:
"requestParameters: I am not sure what the intent of this variable is.
it can mean three different things:
1. Data items passed as part of the action URL - this seems redundant as
the Producer can easily use navigationalState.
2. Data items passed as <form method=get> submit? Is this indeed the case?
3. Data items passed as <form method-post> submit? Is this indeed the case?
Note that (2) and (3) are accessed using the same API in J2EE but not in
ASP, so if the intent is also for (2) and (3) then we may need to
differentiate."
