Home » Adobe Manuals » Computer Software » Adobe 38040334 » Manual Viewer

Adobe 38040334 API Reference - Page 26

MMHttp.postTextCallback, Availability, Description, Arguments

UPC - 883919090467

Add to My Manuals
Save this manual to your list of manuals

Page 26 highlights

DREAMWEAVER CS3 21 API Reference 1 The myScripts.cfm file in the Configuration/DeployScripts folder on the local computer is copied to another folder named DeployScripts, which is a subfolder of the root folder on the ultraqa8 website. To deploy the files, Dreamweaver uses the protocol specified in the site configuration properties. 2 Dreamweaver uses HTTP protocol to post the arg1=Foo data to the web server. 3 As a result of the post request, the web server on ultraqa8 executes the myScripts.cfm script using the arg1 data. MMHttp.postTextCallback() Availability Dreamweaver UltraDev 4, enhanced in Dreamweaver MX. Description Performs an HTTP post of the text to the specified URL and passes the reply from the server to the specified function. Typically, the data associated with a post operation is form-encoded text, but it could be any type of data that the server expects to receive. Arguments callbackFunc, URL, dataToPost, {contentType}, {serverScriptsFolder} • The callbackFunc argument is the name of the JavaScript function to call when the HTTP request is complete. • The URL argument is an absolute URL on a web server; if http:// is omitted from the URL, Dreamweaver assumes HTTP protocol. • The dataToPost argument is the data to be posted. If the third argument is "application/x-www-form-urlencoded" or omitted, data must be form-encoded according to section 8.2.1 of the RFC 1866 specification (available at www.faqs.org/rfcs/rfc1866.html). • The contentType argument, which is optional, is the content type of the data to be posted. If omitted, this argument defaults to "application/x-www-form-urlencoded". • The serverScriptsFolder argument is an optional string. It names a particular folder, relative to the Configuration folder on the application server-to which you want to post the data. To post the data, Dreamweaver uses the appropriate transfer protocol (such as FTP, WebDAV, or Remote File System). Dreamweaver retrieves these data and passes them to the function identified by callbackFunc. If an error occurs, Dreamweaver reports it in the statusCode property of the returned object.

Section	Page
Contents	3
Chapter 1: Introduction	6
Background	7
Extending Dreamweaver	7
Additional resources for extension writers	7
New functions in Dreamweaver CS3	7
Removed functions	9
Errata	10
Conventions used in this guide	10
Chapter 2: The file I/O API	11
Accessing configuration folders	11
The file I/O API	11
Chapter 3: The HTTP API	20
How the HTTP API works	20
The HTTP API	21
Chapter 4: The Design Notes API	27
How Design Notes work	27
The Design Notes JavaScript API	28
The Design Notes C API	32
Chapter 5: Fireworks integration	39
The FWLaunch API	39
Chapter 6: Flash integration	46
How Flash elements work	46
Inserting Flash elements	46
The Flash Objects API	47
Chapter 7: The database API	51
How database API functions work	51
Database connection functions	52
Database access functions	64
Chapter 8: The database connectivity API	76
How to develop a new connection type	76
The Connection API	78
The generated include file	80
The definition file for your connection type	82
Chapter 9: The JavaBeans API	84
The JavaBeans API	84
Chapter 10: The source control integration API	89
How source control integration with Dreamweaver works	90
Adding source control system functionality	90
The source control integration API required functions	90
The source control integration API optional functions	96
Enablers	104
Chapter 11: Application	109
External application functions	109
Global application functions	117
Bridge communication functions	122
Chapter 12: Workspace	124
History functions	124
Insert object functions	132
Keyboard functions	135
Menu functions	141
Results window functions	143
Toggle functions	154
Toolbar functions	173
Window functions	178
Code collapse functions	188
Code view toolbar functions	194
Chapter 13: Site	198
Report functions	198
Site functions	199
Chapter 14: Document	232
Conversion functions	232
Command functions	233
File manipulation functions	235
Global document functions	249
Path functions	258
Selection functions	260
String manipulation functions	267
Translation functions	270
XSLT functions	272
Chapter 15: Page content	275
Assets panel functions	275
Behavior functions	285
Clipboard functions	293
Library and template functions	298
Snippets panel functions	303
Spry widget editing functions	306
Inserting Spry widgets functions	308
Browser compatibility check functions	311
Chapter 16: Dynamic documents	319
Server components functions	319
Data source functions	320
Extension Data Manager functions	321
Live data functions	324
Server behavior functions	328
Server model functions	330
Chapter 17: Design	337
CSS layout functions	337
Frame and frameset functions	356
Layer and image map functions	358
Layout environment functions	360
Layout view functions	365
Zoom functions	374
Guide functions and properties	377
Table editing functions	384
Chapter 18: Code	393
Code functions	393
Find and replace functions	397
General editing functions	402
Print function	417
Quick Tag Editor functions	418
Code view functions	420
Tag editor and tag library functions	436
Chapter 19: Enablers	440
Enabler functions	440

Match case Limit results 1 per page

DREAMWEAVER CS3

API Reference

The myScripts.cfm file in the Configuration/DeployScripts folder on the local computer is copied to another

folder named DeployScripts, which is a subfolder of the root folder on the ultraqa8 website. To deploy the files,

Dreamweaver uses the protocol specified in the site configuration properties.

Dreamweaver uses HTTP protocol to post the

arg1=Foo

data to the web server.

As a result of the post request, the web server on ultraqa8 executes the myScripts.cfm script using the

arg1

data.

MMHttp.postTextCallback()

Availability

Dreamweaver UltraDev 4, enhanced in Dreamweaver MX.

Description

Performs an HTTP post of the text to the specified URL and passes the reply from the server to the specified

function. Typically, the data associated with a post operation is form-encoded text, but it could be any type of data

that the server expects to receive.

Arguments

callbackFunc, URL, dataToPost, {contentType}, {serverScriptsFolder}

•

The

callbackFunc

argument is the name of the JavaScript function to call when the HTTP request is complete.

•

The

URL

argument is an absolute URL on a web server; if http:// is omitted from the URL, Dreamweaver assumes

HTTP protocol.

•

The

dataToPost

argument is the data to be posted. If the third argument is

"application/x-www-form-urlen-

coded"

or omitted,

data

must be form-encoded according to section 8.2.1 of the RFC 1866 specification

(available at

www.faqs.org/rfcs/rfc1866.html

•

The

contentType

argument, which is optional, is the content type of the data to be posted. If omitted, this

argument defaults to

"application/x-www-form-urlencoded"

•

The

serverScriptsFolder

argument is an optional string. It names a particular folder, relative to the Configu-

ration folder on the application server—to which you want to post the data. To post the data, Dreamweaver uses

the appropriate transfer protocol (such as FTP, WebDAV, or Remote File System). Dreamweaver retrieves these

data and passes them to the function identified by

callbackFunc

If an error occurs, Dreamweaver reports it in the

statusCode

property of the returned object.