We've already described how the sample app creates a file in Creating a File. In the target folder and then uploads the data to the new file. To upload a file to a folder managed by SugarSync, an app first creates the file In the Magic Briefcase and then uploads the data from the file in the local directory to the new file. In processing that request, the sample app first creates the file Upload a file from the current local directory to the Magic Briefcase. One type of request that you can make when you use the sample application is Your requests should specify the actual access token created for your application as well as an
Note: The Authorization and User-Agent header field values shown in this and other examples are only illustrative. Notice that your app needs to submit the access token as part of the request. User-Agent: Jakarta Commons-HttpClient/3.1 Here's what the request to upload data to a file might look like: For more information about the resumable upload approach, see Resumable Uploads. Here, we'll focus on the first approach, that is, the simpler approach. However, there is a way to upload data to a file and allow your app to resume the data upload from the point of failure. Your app would have to re-request the entire file data upload. Uploading data to a file creates a new file version in the SugarSync datastore and associates the uploaded data with the newlyĪlthough this approach is relatively simple - it's a one-step process - it's important to understand that if the data upload does not successfully complete, that is, if all the data is not completely uploaded, the approach does notĪllow your app to resume the upload from the point of failure. The PUT request needs to specify the location of the file that contains the source data, as well the size of the data. To upload data to a file, your app needs to issue an HTTP PUT request to the URL that represents In this case, the server doesn't need to know the length of the content before it starts transmitting a response to your app. If your app doesn't know the size of the source data, it can specify chunked transfer encoding. The PUT request needs to specify the location of the file that contains the source data, as well the size of the data (that is, its content length). The URL that represents the data resource for the file is. For example, if the URL that represents the target file is The URL for the data resource is the URL that represents the file followedīy /data. That represents the data resource for the target file. Your app can upload data to a file by issuing an HTTP PUT request to the URL
0 kommentar(er)
