<kendo:upload-async>

Configures the ability to upload a files in an asynchronous manner. Please refer to the async mode help topic for more details.

Example

<kendo:upload>
    <kendo:upload-async></kendo:upload-async>
</kendo:upload>

Configuration Attributes

autoRetryAfter float

If you set the property, the failed upload request is repeated after the declared amount of miliseconds.

Example

<kendo:upload-async autoRetryAfter="autoRetryAfter">
</kendo:upload-async>

autoUpload boolean

The selected files will be uploaded immediately by default. You can change this behavior by setting autoUpload to false.

Example

<kendo:upload-async autoUpload="autoUpload">
</kendo:upload-async>

batch boolean

The selected files will be uploaded in separate requests, if this is supported by the browser. You can change this behavior by setting batch to true, in which case all selected files will be uploaded in one request.The batch mode applies to multiple files, which are selected at the same time. Files selected one after the other will be uploaded in separate requests.

Example

<kendo:upload-async batch="batch">
</kendo:upload-async>

chunkSize float

When the property is set, the selected files are uploaded with the declared size chunk by chunk. Each request sends a separate file blob and additional string metadata to the server. This metadata is in a stringified JSON format and contains the chunkIndex, contentType, totalFileSize, totalChunks, uploadUid properties. These properties enable the validation and combination of the file on the server side. The response also returns a JSON object with the uploaded and fileUid properties, which notifies the client what is the next chunk.You can use this property only when async.batch is set to false.

Example

<kendo:upload-async chunkSize="chunkSize">
</kendo:upload-async>

concurrent boolean

By default, the selected files are uploaded one after another. When set to true, all selected files start uploading simultaneously.This property is available when the async.chunkSize is set.

Example

<kendo:upload-async concurrent="concurrent">
</kendo:upload-async>

maxAutoRetries float

Sets the maximum number of attempts that are performed if an upload fails.The property is only used when the async.autoRetryAfter property is also defined.

Example

<kendo:upload-async maxAutoRetries="maxAutoRetries">
</kendo:upload-async>

removeField java.lang.String

The name of the form field submitted to the Remove URL.

Example

<kendo:upload-async removeField="removeField">
</kendo:upload-async>

removeUrl java.lang.String

The URL of the handler responsible for removing uploaded files (if any). The handler must accept POST requests containing one or more "fileNames" fields specifying the files to be deleted.

Example

<kendo:upload-async removeUrl="removeUrl">
</kendo:upload-async>

removeVerb java.lang.String

The HTTP verb to be used by the remove action.

Example

<kendo:upload-async removeVerb="removeVerb">
</kendo:upload-async>

saveField java.lang.String

The name of the form field submitted to the save URL. The default value is the input name.

Example

<kendo:upload-async saveField="saveField">
</kendo:upload-async>

saveUrl java.lang.String

The URL of the handler that will receive the submitted files. The handler must accept POST requests containing one or more fields with the same name as the original input name.

Example

<kendo:upload-async saveUrl="saveUrl">
</kendo:upload-async>

useArrayBuffer boolean

By default, the files are uploaded as filedata. When set to true, the files are read as file buffer by using FileReader and this buffer is send in the request body.

Example

<kendo:upload-async useArrayBuffer="useArrayBuffer">
</kendo:upload-async>

withCredentials boolean

Controls whether to send credentials (cookies, headers) for cross-site requests. This option will be ignored if the browser doesn't support File API.

Example

<kendo:upload-async withCredentials="withCredentials">
</kendo:upload-async>
Is this article helpful? Yes / No
Thank you for your feedback!

Give article feedback

Tell us how we can improve the information

close
Dummy