Attaching or embedding a file in a request
When you upload or download a file, the content streams to or from the Encyclopedia volume using one of the following methods:
Attach the file in the UploadFile response or DownloadFile request using HTTP chunked transfer encoding. Chunked transfer encoding breaks the data into discrete sections, or chunks, and sends them in a series. This method is useful when the file is long and when BIRT iHub begins sending the response before retrieving all the data. An attachment relies on maintaining a persistent connection, which is the default setting for HTTP 1.1. This method frees BIRT iHub between sections, though the connection remains open. The values used for chunking files must be precise, or the SOAP message may hang.
Embed the file in the UploadFile response or DownloadFile request and send the message as a single block. Embedding works best with smaller files. To embed a file, specify a ContentLength in the HTTP header instead of chunked transfer encoding. If you use HTTP 1.0, you typically choose to embed the file.
Although BIRT iHub System supports both methods, Actuate operations typically use attachments.
A chunked message consists of three parts:
An HTTP header
An Actuate SOAP message such as UploadFile or DownloadFile
A file to embed or attach