Share via

3.2.4.1.4.1 Methods

  • Article

cAcceptUpload: This method is called by the server to notify the client that the server is ready, and the client can proceed with the upload for the content that corresponds to the specified cookie. The client can proceed to upload the package when it receives the call.

  • cookie (Int32): The unique cookie value that corresponds to the content.

  • stream (DistributedObject): The UploadStream distributed object that the client uses to upload the content package, where DistributedObject is defined in section 3.1.1.1.4.

cRejectUpload: This method is called by the server to notify the client that the content upload request with the specific cookie is rejected and any further calls with the given cookie MUST NOT be made. After the client calls sRequestUpload, the server MUST respond with cRejectUpload or cAcceptUpload.

  • cookie(int32): The unique cookie value that corresponds to the content.

  • reason (Int32): A reason code for rejecting the upload. See the preceding table for the response codes.

cUploadFinished: This method is called by the server to notify the upload client that the server finished processing the content upload that corresponds to the specific cookie. The function is called in both success and failure cases.

  • cookie (Int32): The unique cookie value that corresponds to the content.

  • reason (Int32): The reason that the upload finished. In failure cases, the parameter specifies the reason of the failure.

cSetAvailableSpace: This method is called by the server to notify the client that the storage space is available on the server. It is currently deprecated.

  • size (Int64): Specifies the number of bytes available on the server.

cAcceptWebUpload<16>: This method is called by the server to notify the client that the server sRequestWebUploadBlob method has succeeded. The client responds by starting to upload a file using the provided uploadUrl value. It is guaranteed that at least one client attempt will be allowed for uploading a file content using the browser POST form upload HTTPS request.

cAcceptWebDownload<17>: This method is called by the server to notify the client that the server sRequestWebDownloadBlob method has succeeded. The client SHOULD respond by starting to download a file using the provided downloadUrl value. It is guaranteed that at least one client attempt will be allowed for downloading a file using the browser GET HTTPS request

  • Cookie (Int32): The unique cookie value that corresponds to the original client request.

  • downloadUrl(String): A Url to use for download an unencrypted file using GET  HTTPS request.

cRejectWebDownload<18>:  This method is called by the server to notify the client that the server sRequestWebDownloadBlob method has failed.

  • Cookie (Int32): The unique cookie value that corresponds to the original client request.

  • reason (Int32): The reason why sRequestWebDownloadBlob request has failed.

The following table lists the DownloadFinishReason<19> response codes.

       Response code

Numeric value

Description

Ok

0

Success (reserved and currently is never used).

NotAuthorized

1

The user was not authorized to download this file.

NotFound

2

The specified filename is not found.

NotSupported

3

This conference does not support decrypted files download using the HTTPS GET request.

UnknownFailure

4

Unknown failure.