AddLongstring (HttpRequest subroutine): Difference between revisions

From m204wiki
Jump to navigation Jump to search
m (edits, tags and links)
m (rematch syntax terms to syntax diagram after it was updated)
Line 12: Line 12:
<td>A previously defined and instantiated <var>HttpRequest</var> object.
<td>A previously defined and instantiated <var>HttpRequest</var> object.
</td></tr>
</td></tr>
<tr><th>ls</th>
<tr><th>string</th>
<td>A <var>longstring</var> variable.
<td>A <var>[[Longstrings|Longstring]]</var> variable.
</td></tr>
</td></tr>
<tr><th>binflag</th>
<tr><th>xlatFlag</th>
<td>A numeric expression that, if nonzero, indicates binary data. Setting this option overrides the default behaviour of translating EBCDIC to ASCII.   
<td>A numeric expression that, if nonzero, indicates binary data. Setting this option overrides the default behaviour of translating EBCDIC to ASCII.   
</td></tr></table>
</td></tr></table>

Revision as of 05:11, 19 June 2011

Add a longstring to POST data for this request (HttpRequest class)

The AddLongString subroutine adds the contents of a Longstring to the HTTP Post data that is subsequently sent on a Post method invocation.

The contents of the passed Longstring become the post data of the request being built. Invoking this method erases any post data previously added by AddXml or AddLongString method calls. By default, the data is converted from EBCDIC to ASCII; however, this can be turned off.

Syntax

httpRequest:AddLongString( string, [xlatFlag])

Syntax terms

httpRequest A previously defined and instantiated HttpRequest object.
string A Longstring variable.
xlatFlag A numeric expression that, if nonzero, indicates binary data. Setting this option overrides the default behaviour of translating EBCDIC to ASCII.

Usage notes

  • Unlike the AddField method, AddLongString has no effect on the request content type.

See also