W3C home > Mailing lists > Public > www-voice@w3.org > July to September 2002

Re: using get or post method in submit elementMOVE TO ANOTHER E-MAIL LIST

From: Al Gilman <asgilman@iamdigex.net>
Date: Thu, 15 Aug 2002 16:38:03 -0400
Message-Id: <>
To: Jim Larson <jim@larson-tech.com>, "Wyss, Felix" <FelixW@inin.com>
Cc: Dave Burke <david.burke@voxpilot.com>, www-voice@w3.org, "Robert S. Willner" <rwillner@telcordia.com>

At 02:57 PM 2002-08-15, Jim Larson wrote:
   I'd appreciate your moving this discussion to another list.

a) Read

  TAG Finding: URIs, Addressability, and the use of HTTP GET

b) Try <www-talk@w3.org> as the list if still not clear.


>Folks, this e-mail list is intended to report problems with VoiceXML and 
>related speech application langauges to the attention of the W3C Voice 
>Browser Working Group.  While your discussion is interesting, it is 
>outside the intended scope of this e-mail list.  I'd appreciate your 
>moving this discussion to another list.
>Jim Larson
>Chair, Voice Browser Working Group
>Wyss, Felix wrote:
>>In addition, I would consider it bad style, if not a violation of the 
>>semantics of HTTP, to modify state on the server with a GET method (such 
>>as updating a database).
>>-----Original Message-----
>>From: Dave Burke 
>>Sent: Wednesday, August 14, 2002 18:01
>>To: <mailto:www-voice@w3.org>www-voice@w3.org; Robert S. Willner
>>Subject: Re: using get or post method in submit element
>>Hi Robert,
>>The GET and POST methods are contained within the HTTP 1.1 specification
>>(RFC2616). The VoiceXML 2.0 spec. in turn references the HTTP spec. and thus
>>the two methods supported by <submit> are not vendor specific but standard.
>>GET vs POST depends on what the application developer wants to do. GET sends
>>data (submit's namelist) as part of the URL. POST on t
>>he other hand sends it
>>as part of the body. Generally, POST is better for sending large amounts of
>>data and also for sending user specific data (using GET usually results in a
>>log entry in web servers for the requested URL and thus includes the data
>>sent). GET might be simpler for some server side scripts (it is easier to
>>debug at least) and also might be useful if the requested resource needs to
>>be cached. Finally, there are two common encodings that POST uses and both
>>of these must be supported by VoiceXML 2.0 conforming interpreters. These
>>are 'application/x-www-form-urlencoded' and 'multipart/form-data'. The
>>former is typically used to send variables (as strings) and the later used
>>to send binary data (such as a recording via the <record> tag).
>>Hope this helps,
>>----- Original Message -----
>>From: "Robert S. Willner" <mailto:rwillner@telcordia.com><rwillner@telcord
>>To: <mailto:www-voice@w3.org><www-voice@w3.org>
>>Sent: Wednesday, August 14, 2002 11:37 PM
>>Subject: using get or post method in submit element
>>>Please provide information on the use of get versus post with the submit
>>>What are the implications of using the get method versus the post method
>>>the submit element? Is this a vendor-specific implementation issue or is
>>>there an expected behavior for each method?
>>>Robert Willner
>>>Telcordia Technologies
Received on Thursday, 15 August 2002 16:38:41 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:07:36 UTC