com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For example, when users upload or modify an existing file, a new Item
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For example, when users upload or modify an existing file, a new Item
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Prepares the links for uploading files to the target Folder.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* populated based on the upload method, provider, and canResume parameters passed to the
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload call.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* There are two different URLs for upload: /sf/v3/Items(id)/Upload accepts parameters
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* to retrieve the Item ID of the file after the upload is completed.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw" (if the parameter raw=true
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* is provided to the Uploader) or use MIME multi-part form encoding otherwise. Raw uploads
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For Streamed and Threaded uploads, if the CanResume parameter is specified in the call to Upload,
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload with that specification and is ready to resume the upload process. The client can
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* ResumeOffset. If the client decides to restart the upload, it should simply ignore the resume
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw, String fileName, Long fileSize, String batchId, Boolean batchLast, Boolean canResume, Boolean startOver, Boolean unzip, String tool, Boolean overwrite, String title, String details, Boolean isSend, String sendGuid, String opid, Integer threadCount, String responseFormat, Boolean notify, Date clientCreatedDateUTC, Date clientModifiedDateUTC, Integer expirationDays) throws InvalidOrMissingParameterException 	{
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Prepares the links for uploading files to the target Folder.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* populated based on the upload method, provider, and canResume parameters passed to the
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload call.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* There are two different URLs for upload: /sf/v3/Items(id)/Upload accepts parameters
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* to retrieve the Item ID of the file after the upload is completed.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw" (if the parameter raw=true
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* is provided to the Uploader) or use MIME multi-part form encoding otherwise. Raw uploads
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For Streamed and Threaded uploads, if the CanResume parameter is specified in the call to Upload,
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload with that specification and is ready to resume the upload process. The client can
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* ResumeOffset. If the client decides to restart the upload, it should simply ignore the resume
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw, String fileName, Long fileSize, String batchId, Boolean batchLast, Boolean canResume, Boolean startOver, Boolean unzip, String tool, Boolean overwrite, String title, String details, Boolean isSend, String sendGuid, String opid, Integer threadCount, String responseFormat, Boolean notify, Date clientCreatedDateUTC, Date clientModifiedDateUTC) throws InvalidOrMissingParameterException 	{
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Prepares the links for uploading files to the target Folder.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* populated based on the upload method, provider, and canResume parameters passed to the
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload call.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* There are two different URLs for upload: /sf/v3/Items(id)/Upload accepts parameters
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* to retrieve the Item ID of the file after the upload is completed.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw" (if the parameter raw=true
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* is provided to the Uploader) or use MIME multi-part form encoding otherwise. Raw uploads
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For Streamed and Threaded uploads, if the CanResume parameter is specified in the call to Upload,
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload with that specification and is ready to resume the upload process. The client can
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* ResumeOffset. If the client decides to restart the upload, it should simply ignore the resume
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw, String fileName, Long fileSize, String batchId, Boolean batchLast, Boolean canResume, Boolean startOver, Boolean unzip, String tool, Boolean overwrite, String title, String details, Boolean isSend, String sendGuid, String opid, Integer threadCount, String responseFormat, Boolean notify, Date clientCreatedDateUTC) throws InvalidOrMissingParameterException 	{
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Prepares the links for uploading files to the target Folder.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* populated based on the upload method, provider, and canResume parameters passed to the
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload call.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* There are two different URLs for upload: /sf/v3/Items(id)/Upload accepts parameters
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* to retrieve the Item ID of the file after the upload is completed.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw" (if the parameter raw=true
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* is provided to the Uploader) or use MIME multi-part form encoding otherwise. Raw uploads
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For Streamed and Threaded uploads, if the CanResume parameter is specified in the call to Upload,
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload with that specification and is ready to resume the upload process. The client can
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* ResumeOffset. If the client decides to restart the upload, it should simply ignore the resume
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw, String fileName, Long fileSize, String batchId, Boolean batchLast, Boolean canResume, Boolean startOver, Boolean unzip, String tool, Boolean overwrite, String title, String details, Boolean isSend, String sendGuid, String opid, Integer threadCount, String responseFormat, Boolean notify) throws InvalidOrMissingParameterException 	{
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Prepares the links for uploading files to the target Folder.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* populated based on the upload method, provider, and canResume parameters passed to the
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload call.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* There are two different URLs for upload: /sf/v3/Items(id)/Upload accepts parameters
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* to retrieve the Item ID of the file after the upload is completed.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw" (if the parameter raw=true
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* is provided to the Uploader) or use MIME multi-part form encoding otherwise. Raw uploads
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For Streamed and Threaded uploads, if the CanResume parameter is specified in the call to Upload,
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload with that specification and is ready to resume the upload process. The client can
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* ResumeOffset. If the client decides to restart the upload, it should simply ignore the resume
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw, String fileName, Long fileSize, String batchId, Boolean batchLast, Boolean canResume, Boolean startOver, Boolean unzip, String tool, Boolean overwrite, String title, String details, Boolean isSend, String sendGuid, String opid, Integer threadCount, String responseFormat) throws InvalidOrMissingParameterException 	{
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Prepares the links for uploading files to the target Folder.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* populated based on the upload method, provider, and canResume parameters passed to the
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload call.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* There are two different URLs for upload: /sf/v3/Items(id)/Upload accepts parameters
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* to retrieve the Item ID of the file after the upload is completed.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw" (if the parameter raw=true
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* is provided to the Uploader) or use MIME multi-part form encoding otherwise. Raw uploads
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For Streamed and Threaded uploads, if the CanResume parameter is specified in the call to Upload,
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload with that specification and is ready to resume the upload process. The client can
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* ResumeOffset. If the client decides to restart the upload, it should simply ignore the resume
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw, String fileName, Long fileSize, String batchId, Boolean batchLast, Boolean canResume, Boolean startOver, Boolean unzip, String tool, Boolean overwrite, String title, String details, Boolean isSend, String sendGuid, String opid, Integer threadCount) throws InvalidOrMissingParameterException 	{
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Prepares the links for uploading files to the target Folder.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* populated based on the upload method, provider, and canResume parameters passed to the
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload call.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* There are two different URLs for upload: /sf/v3/Items(id)/Upload accepts parameters
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* to retrieve the Item ID of the file after the upload is completed.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw" (if the parameter raw=true
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* is provided to the Uploader) or use MIME multi-part form encoding otherwise. Raw uploads
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For Streamed and Threaded uploads, if the CanResume parameter is specified in the call to Upload,
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload with that specification and is ready to resume the upload process. The client can
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* ResumeOffset. If the client decides to restart the upload, it should simply ignore the resume
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw, String fileName, Long fileSize, String batchId, Boolean batchLast, Boolean canResume, Boolean startOver, Boolean unzip, String tool, Boolean overwrite, String title, String details, Boolean isSend, String sendGuid, String opid) throws InvalidOrMissingParameterException 	{
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Prepares the links for uploading files to the target Folder.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* populated based on the upload method, provider, and canResume parameters passed to the
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload call.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* There are two different URLs for upload: /sf/v3/Items(id)/Upload accepts parameters
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* to retrieve the Item ID of the file after the upload is completed.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw" (if the parameter raw=true
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* is provided to the Uploader) or use MIME multi-part form encoding otherwise. Raw uploads
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For Streamed and Threaded uploads, if the CanResume parameter is specified in the call to Upload,
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload with that specification and is ready to resume the upload process. The client can
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* ResumeOffset. If the client decides to restart the upload, it should simply ignore the resume
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw, String fileName, Long fileSize, String batchId, Boolean batchLast, Boolean canResume, Boolean startOver, Boolean unzip, String tool, Boolean overwrite, String title, String details, Boolean isSend, String sendGuid) throws InvalidOrMissingParameterException 	{
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Prepares the links for uploading files to the target Folder.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* populated based on the upload method, provider, and canResume parameters passed to the
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload call.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* There are two different URLs for upload: /sf/v3/Items(id)/Upload accepts parameters
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* to retrieve the Item ID of the file after the upload is completed.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw" (if the parameter raw=true
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* is provided to the Uploader) or use MIME multi-part form encoding otherwise. Raw uploads
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For Streamed and Threaded uploads, if the CanResume parameter is specified in the call to Upload,
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload with that specification and is ready to resume the upload process. The client can
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* ResumeOffset. If the client decides to restart the upload, it should simply ignore the resume
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw, String fileName, Long fileSize, String batchId, Boolean batchLast, Boolean canResume, Boolean startOver, Boolean unzip, String tool, Boolean overwrite, String title, String details, Boolean isSend) throws InvalidOrMissingParameterException 	{
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Prepares the links for uploading files to the target Folder.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* populated based on the upload method, provider, and canResume parameters passed to the
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload call.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* There are two different URLs for upload: /sf/v3/Items(id)/Upload accepts parameters
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* to retrieve the Item ID of the file after the upload is completed.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw" (if the parameter raw=true
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* is provided to the Uploader) or use MIME multi-part form encoding otherwise. Raw uploads
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For Streamed and Threaded uploads, if the CanResume parameter is specified in the call to Upload,
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload with that specification and is ready to resume the upload process. The client can
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* ResumeOffset. If the client decides to restart the upload, it should simply ignore the resume
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw, String fileName, Long fileSize, String batchId, Boolean batchLast, Boolean canResume, Boolean startOver, Boolean unzip, String tool, Boolean overwrite, String title, String details) throws InvalidOrMissingParameterException 	{
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Prepares the links for uploading files to the target Folder.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* populated based on the upload method, provider, and canResume parameters passed to the
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload call.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* There are two different URLs for upload: /sf/v3/Items(id)/Upload accepts parameters
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* to retrieve the Item ID of the file after the upload is completed.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw" (if the parameter raw=true
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* is provided to the Uploader) or use MIME multi-part form encoding otherwise. Raw uploads
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For Streamed and Threaded uploads, if the CanResume parameter is specified in the call to Upload,
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload with that specification and is ready to resume the upload process. The client can
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* ResumeOffset. If the client decides to restart the upload, it should simply ignore the resume
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw, String fileName, Long fileSize, String batchId, Boolean batchLast, Boolean canResume, Boolean startOver, Boolean unzip, String tool, Boolean overwrite, String title) throws InvalidOrMissingParameterException 	{
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Prepares the links for uploading files to the target Folder.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* populated based on the upload method, provider, and canResume parameters passed to the
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload call.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* There are two different URLs for upload: /sf/v3/Items(id)/Upload accepts parameters
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* to retrieve the Item ID of the file after the upload is completed.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw" (if the parameter raw=true
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* is provided to the Uploader) or use MIME multi-part form encoding otherwise. Raw uploads
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For Streamed and Threaded uploads, if the CanResume parameter is specified in the call to Upload,
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload with that specification and is ready to resume the upload process. The client can
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* ResumeOffset. If the client decides to restart the upload, it should simply ignore the resume
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw, String fileName, Long fileSize, String batchId, Boolean batchLast, Boolean canResume, Boolean startOver, Boolean unzip, String tool, Boolean overwrite) throws InvalidOrMissingParameterException 	{
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Prepares the links for uploading files to the target Folder.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* populated based on the upload method, provider, and canResume parameters passed to the
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload call.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* There are two different URLs for upload: /sf/v3/Items(id)/Upload accepts parameters
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* to retrieve the Item ID of the file after the upload is completed.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw" (if the parameter raw=true
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* is provided to the Uploader) or use MIME multi-part form encoding otherwise. Raw uploads
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For Streamed and Threaded uploads, if the CanResume parameter is specified in the call to Upload,
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload with that specification and is ready to resume the upload process. The client can
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* ResumeOffset. If the client decides to restart the upload, it should simply ignore the resume
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw, String fileName, Long fileSize, String batchId, Boolean batchLast, Boolean canResume, Boolean startOver, Boolean unzip, String tool) throws InvalidOrMissingParameterException 	{
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Prepares the links for uploading files to the target Folder.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* populated based on the upload method, provider, and canResume parameters passed to the
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload call.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* There are two different URLs for upload: /sf/v3/Items(id)/Upload accepts parameters
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* to retrieve the Item ID of the file after the upload is completed.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw" (if the parameter raw=true
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* is provided to the Uploader) or use MIME multi-part form encoding otherwise. Raw uploads
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For Streamed and Threaded uploads, if the CanResume parameter is specified in the call to Upload,
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload with that specification and is ready to resume the upload process. The client can
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* ResumeOffset. If the client decides to restart the upload, it should simply ignore the resume
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw, String fileName, Long fileSize, String batchId, Boolean batchLast, Boolean canResume, Boolean startOver, Boolean unzip) throws InvalidOrMissingParameterException 	{
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Prepares the links for uploading files to the target Folder.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* populated based on the upload method, provider, and canResume parameters passed to the
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload call.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* There are two different URLs for upload: /sf/v3/Items(id)/Upload accepts parameters
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* to retrieve the Item ID of the file after the upload is completed.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw" (if the parameter raw=true
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* is provided to the Uploader) or use MIME multi-part form encoding otherwise. Raw uploads
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For Streamed and Threaded uploads, if the CanResume parameter is specified in the call to Upload,
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload with that specification and is ready to resume the upload process. The client can
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* ResumeOffset. If the client decides to restart the upload, it should simply ignore the resume
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw, String fileName, Long fileSize, String batchId, Boolean batchLast, Boolean canResume, Boolean startOver) throws InvalidOrMissingParameterException 	{
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Prepares the links for uploading files to the target Folder.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* populated based on the upload method, provider, and canResume parameters passed to the
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload call.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* There are two different URLs for upload: /sf/v3/Items(id)/Upload accepts parameters
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* to retrieve the Item ID of the file after the upload is completed.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw" (if the parameter raw=true
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* is provided to the Uploader) or use MIME multi-part form encoding otherwise. Raw uploads
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For Streamed and Threaded uploads, if the CanResume parameter is specified in the call to Upload,
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload with that specification and is ready to resume the upload process. The client can
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* ResumeOffset. If the client decides to restart the upload, it should simply ignore the resume
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw, String fileName, Long fileSize, String batchId, Boolean batchLast, Boolean canResume) throws InvalidOrMissingParameterException 	{
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Prepares the links for uploading files to the target Folder.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* populated based on the upload method, provider, and canResume parameters passed to the
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload call.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* There are two different URLs for upload: /sf/v3/Items(id)/Upload accepts parameters
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* to retrieve the Item ID of the file after the upload is completed.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw" (if the parameter raw=true
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* is provided to the Uploader) or use MIME multi-part form encoding otherwise. Raw uploads
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For Streamed and Threaded uploads, if the CanResume parameter is specified in the call to Upload,
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload with that specification and is ready to resume the upload process. The client can
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* ResumeOffset. If the client decides to restart the upload, it should simply ignore the resume
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw, String fileName, Long fileSize, String batchId, Boolean batchLast) throws InvalidOrMissingParameterException 	{
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Prepares the links for uploading files to the target Folder.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* populated based on the upload method, provider, and canResume parameters passed to the
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload call.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* There are two different URLs for upload: /sf/v3/Items(id)/Upload accepts parameters
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* to retrieve the Item ID of the file after the upload is completed.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw" (if the parameter raw=true
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* is provided to the Uploader) or use MIME multi-part form encoding otherwise. Raw uploads
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For Streamed and Threaded uploads, if the CanResume parameter is specified in the call to Upload,
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload with that specification and is ready to resume the upload process. The client can
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* ResumeOffset. If the client decides to restart the upload, it should simply ignore the resume
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw, String fileName, Long fileSize, String batchId) throws InvalidOrMissingParameterException 	{
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Prepares the links for uploading files to the target Folder.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* populated based on the upload method, provider, and canResume parameters passed to the
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload call.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* There are two different URLs for upload: /sf/v3/Items(id)/Upload accepts parameters
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* to retrieve the Item ID of the file after the upload is completed.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw" (if the parameter raw=true
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* is provided to the Uploader) or use MIME multi-part form encoding otherwise. Raw uploads
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For Streamed and Threaded uploads, if the CanResume parameter is specified in the call to Upload,
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload with that specification and is ready to resume the upload process. The client can
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* ResumeOffset. If the client decides to restart the upload, it should simply ignore the resume
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw, String fileName, Long fileSize) throws InvalidOrMissingParameterException 	{
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Prepares the links for uploading files to the target Folder.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* populated based on the upload method, provider, and canResume parameters passed to the
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload call.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* There are two different URLs for upload: /sf/v3/Items(id)/Upload accepts parameters
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* to retrieve the Item ID of the file after the upload is completed.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw" (if the parameter raw=true
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* is provided to the Uploader) or use MIME multi-part form encoding otherwise. Raw uploads
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For Streamed and Threaded uploads, if the CanResume parameter is specified in the call to Upload,
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload with that specification and is ready to resume the upload process. The client can
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* ResumeOffset. If the client decides to restart the upload, it should simply ignore the resume
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw, String fileName) throws InvalidOrMissingParameterException 	{
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Prepares the links for uploading files to the target Folder.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* populated based on the upload method, provider, and canResume parameters passed to the
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload call.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* There are two different URLs for upload: /sf/v3/Items(id)/Upload accepts parameters
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* to retrieve the Item ID of the file after the upload is completed.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw" (if the parameter raw=true
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* is provided to the Uploader) or use MIME multi-part form encoding otherwise. Raw uploads
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For Streamed and Threaded uploads, if the CanResume parameter is specified in the call to Upload,
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload with that specification and is ready to resume the upload process. The client can
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* ResumeOffset. If the client decides to restart the upload, it should simply ignore the resume
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw) throws InvalidOrMissingParameterException 	{
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Prepares the links for uploading files to the target Folder.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* populated based on the upload method, provider, and canResume parameters passed to the
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload call.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* There are two different URLs for upload: /sf/v3/Items(id)/Upload accepts parameters
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* to retrieve the Item ID of the file after the upload is completed.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw" (if the parameter raw=true
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* is provided to the Uploader) or use MIME multi-part form encoding otherwise. Raw uploads
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For Streamed and Threaded uploads, if the CanResume parameter is specified in the call to Upload,
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload with that specification and is ready to resume the upload process. The client can
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* ResumeOffset. If the client decides to restart the upload, it should simply ignore the resume
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method) throws InvalidOrMissingParameterException 	{
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Prepares the links for uploading files to the target Folder.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* populated based on the upload method, provider, and canResume parameters passed to the
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload call.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* There are two different URLs for upload: /sf/v3/Items(id)/Upload accepts parameters
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* to retrieve the Item ID of the file after the upload is completed.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw" (if the parameter raw=true
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* is provided to the Uploader) or use MIME multi-part form encoding otherwise. Raw uploads
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For Streamed and Threaded uploads, if the CanResume parameter is specified in the call to Upload,
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload with that specification and is ready to resume the upload process. The client can
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* ResumeOffset. If the client decides to restart the upload, it should simply ignore the resume
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
com\citrix\sharefile\api\entities\SFItemsEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
com\citrix\sharefile\api\entities\SFItemsEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url) throws InvalidOrMissingParameterException 	{
com\citrix\sharefile\api\entities\SFItemsEntity.java:	public ISFQuery<SFUploadSpecification> upload2(URI url, SFUploadRequestParams uploadParams, Integer expirationDays) throws InvalidOrMissingParameterException 	{
com\citrix\sharefile\api\entities\SFItemsEntity.java:		if (uploadParams == null) {
com\citrix\sharefile\api\entities\SFItemsEntity.java:			throw new InvalidOrMissingParameterException("uploadParams");
com\citrix\sharefile\api\entities\SFItemsEntity.java:		sfApiQuery.setBody(uploadParams);
com\citrix\sharefile\api\entities\SFItemsEntity.java:	public ISFQuery<SFUploadSpecification> upload2(URI url, SFUploadRequestParams uploadParams) throws InvalidOrMissingParameterException 	{
com\citrix\sharefile\api\entities\SFItemsEntity.java:		if (uploadParams == null) {
com\citrix\sharefile\api\entities\SFItemsEntity.java:			throw new InvalidOrMissingParameterException("uploadParams");
com\citrix\sharefile\api\entities\SFItemsEntity.java:		sfApiQuery.setBody(uploadParams);
com\citrix\sharefile\api\entities\SFRemoteUploadsEntity.java:	public ISFQuery<SFUploadSpecification> upload2(URI url, SFRemoteUploadRequestParams uploadParams, String userId, Integer expirationDays) throws InvalidOrMissingParameterException 	{
com\citrix\sharefile\api\entities\SFRemoteUploadsEntity.java:		if (uploadParams == null) {
com\citrix\sharefile\api\entities\SFRemoteUploadsEntity.java:			throw new InvalidOrMissingParameterException("uploadParams");
com\citrix\sharefile\api\entities\SFRemoteUploadsEntity.java:		sfApiQuery.setBody(uploadParams);
com\citrix\sharefile\api\entities\SFRemoteUploadsEntity.java:	public ISFQuery<SFUploadSpecification> upload2(URI url, SFRemoteUploadRequestParams uploadParams, String userId) throws InvalidOrMissingParameterException 	{
com\citrix\sharefile\api\entities\SFRemoteUploadsEntity.java:		if (uploadParams == null) {
com\citrix\sharefile\api\entities\SFRemoteUploadsEntity.java:			throw new InvalidOrMissingParameterException("uploadParams");
com\citrix\sharefile\api\entities\SFRemoteUploadsEntity.java:		sfApiQuery.setBody(uploadParams);
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Sends an Email to the specified list of addresses, containing a link to files upload.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Sends an Email to the specified list of addresses, containing a link to a download or an upload.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Prepares the links for uploading files to the target Share.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* populated based on the upload method, provider, and resume parameters passed to the
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* upload call.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw", if the "Raw" parameter
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* was provided to the Uploader, or use MIME multi-part form encoding otherwise. Raw uploads
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* it indicates that the server has identified a partial upload with that specification, and is
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders: the result code for the HTTP POST calls to Chunk and Finish Uri can either
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw, String fileName, Long fileSize, String batchId, Boolean batchLast, Boolean canResume, Boolean startOver, Boolean unzip, String tool, Boolean overwrite, String title, String details, Boolean isSend, String sendGuid, String opid, Integer threadCount, String responseFormat, Boolean notify, Date clientCreatedDateUTC, Date clientModifiedDateUTC, Integer expirationDays) throws InvalidOrMissingParameterException 	{
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Prepares the links for uploading files to the target Share.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* populated based on the upload method, provider, and resume parameters passed to the
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* upload call.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw", if the "Raw" parameter
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* was provided to the Uploader, or use MIME multi-part form encoding otherwise. Raw uploads
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* it indicates that the server has identified a partial upload with that specification, and is
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders: the result code for the HTTP POST calls to Chunk and Finish Uri can either
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw, String fileName, Long fileSize, String batchId, Boolean batchLast, Boolean canResume, Boolean startOver, Boolean unzip, String tool, Boolean overwrite, String title, String details, Boolean isSend, String sendGuid, String opid, Integer threadCount, String responseFormat, Boolean notify, Date clientCreatedDateUTC, Date clientModifiedDateUTC) throws InvalidOrMissingParameterException 	{
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Prepares the links for uploading files to the target Share.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* populated based on the upload method, provider, and resume parameters passed to the
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* upload call.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw", if the "Raw" parameter
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* was provided to the Uploader, or use MIME multi-part form encoding otherwise. Raw uploads
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* it indicates that the server has identified a partial upload with that specification, and is
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders: the result code for the HTTP POST calls to Chunk and Finish Uri can either
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw, String fileName, Long fileSize, String batchId, Boolean batchLast, Boolean canResume, Boolean startOver, Boolean unzip, String tool, Boolean overwrite, String title, String details, Boolean isSend, String sendGuid, String opid, Integer threadCount, String responseFormat, Boolean notify, Date clientCreatedDateUTC) throws InvalidOrMissingParameterException 	{
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Prepares the links for uploading files to the target Share.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* populated based on the upload method, provider, and resume parameters passed to the
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* upload call.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw", if the "Raw" parameter
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* was provided to the Uploader, or use MIME multi-part form encoding otherwise. Raw uploads
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* it indicates that the server has identified a partial upload with that specification, and is
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders: the result code for the HTTP POST calls to Chunk and Finish Uri can either
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw, String fileName, Long fileSize, String batchId, Boolean batchLast, Boolean canResume, Boolean startOver, Boolean unzip, String tool, Boolean overwrite, String title, String details, Boolean isSend, String sendGuid, String opid, Integer threadCount, String responseFormat, Boolean notify) throws InvalidOrMissingParameterException 	{
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Prepares the links for uploading files to the target Share.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* populated based on the upload method, provider, and resume parameters passed to the
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* upload call.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw", if the "Raw" parameter
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* was provided to the Uploader, or use MIME multi-part form encoding otherwise. Raw uploads
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* it indicates that the server has identified a partial upload with that specification, and is
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders: the result code for the HTTP POST calls to Chunk and Finish Uri can either
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw, String fileName, Long fileSize, String batchId, Boolean batchLast, Boolean canResume, Boolean startOver, Boolean unzip, String tool, Boolean overwrite, String title, String details, Boolean isSend, String sendGuid, String opid, Integer threadCount, String responseFormat) throws InvalidOrMissingParameterException 	{
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Prepares the links for uploading files to the target Share.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* populated based on the upload method, provider, and resume parameters passed to the
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* upload call.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw", if the "Raw" parameter
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* was provided to the Uploader, or use MIME multi-part form encoding otherwise. Raw uploads
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* it indicates that the server has identified a partial upload with that specification, and is
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders: the result code for the HTTP POST calls to Chunk and Finish Uri can either
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw, String fileName, Long fileSize, String batchId, Boolean batchLast, Boolean canResume, Boolean startOver, Boolean unzip, String tool, Boolean overwrite, String title, String details, Boolean isSend, String sendGuid, String opid, Integer threadCount) throws InvalidOrMissingParameterException 	{
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Prepares the links for uploading files to the target Share.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* populated based on the upload method, provider, and resume parameters passed to the
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* upload call.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw", if the "Raw" parameter
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* was provided to the Uploader, or use MIME multi-part form encoding otherwise. Raw uploads
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* it indicates that the server has identified a partial upload with that specification, and is
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders: the result code for the HTTP POST calls to Chunk and Finish Uri can either
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw, String fileName, Long fileSize, String batchId, Boolean batchLast, Boolean canResume, Boolean startOver, Boolean unzip, String tool, Boolean overwrite, String title, String details, Boolean isSend, String sendGuid, String opid) throws InvalidOrMissingParameterException 	{
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Prepares the links for uploading files to the target Share.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* populated based on the upload method, provider, and resume parameters passed to the
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* upload call.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw", if the "Raw" parameter
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* was provided to the Uploader, or use MIME multi-part form encoding otherwise. Raw uploads
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* it indicates that the server has identified a partial upload with that specification, and is
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders: the result code for the HTTP POST calls to Chunk and Finish Uri can either
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw, String fileName, Long fileSize, String batchId, Boolean batchLast, Boolean canResume, Boolean startOver, Boolean unzip, String tool, Boolean overwrite, String title, String details, Boolean isSend, String sendGuid) throws InvalidOrMissingParameterException 	{
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Prepares the links for uploading files to the target Share.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* populated based on the upload method, provider, and resume parameters passed to the
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* upload call.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw", if the "Raw" parameter
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* was provided to the Uploader, or use MIME multi-part form encoding otherwise. Raw uploads
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* it indicates that the server has identified a partial upload with that specification, and is
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders: the result code for the HTTP POST calls to Chunk and Finish Uri can either
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw, String fileName, Long fileSize, String batchId, Boolean batchLast, Boolean canResume, Boolean startOver, Boolean unzip, String tool, Boolean overwrite, String title, String details, Boolean isSend) throws InvalidOrMissingParameterException 	{
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Prepares the links for uploading files to the target Share.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* populated based on the upload method, provider, and resume parameters passed to the
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* upload call.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw", if the "Raw" parameter
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* was provided to the Uploader, or use MIME multi-part form encoding otherwise. Raw uploads
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* it indicates that the server has identified a partial upload with that specification, and is
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders: the result code for the HTTP POST calls to Chunk and Finish Uri can either
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw, String fileName, Long fileSize, String batchId, Boolean batchLast, Boolean canResume, Boolean startOver, Boolean unzip, String tool, Boolean overwrite, String title, String details) throws InvalidOrMissingParameterException 	{
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Prepares the links for uploading files to the target Share.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* populated based on the upload method, provider, and resume parameters passed to the
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* upload call.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw", if the "Raw" parameter
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* was provided to the Uploader, or use MIME multi-part form encoding otherwise. Raw uploads
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* it indicates that the server has identified a partial upload with that specification, and is
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders: the result code for the HTTP POST calls to Chunk and Finish Uri can either
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw, String fileName, Long fileSize, String batchId, Boolean batchLast, Boolean canResume, Boolean startOver, Boolean unzip, String tool, Boolean overwrite, String title) throws InvalidOrMissingParameterException 	{
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Prepares the links for uploading files to the target Share.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* populated based on the upload method, provider, and resume parameters passed to the
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* upload call.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw", if the "Raw" parameter
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* was provided to the Uploader, or use MIME multi-part form encoding otherwise. Raw uploads
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* it indicates that the server has identified a partial upload with that specification, and is
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders: the result code for the HTTP POST calls to Chunk and Finish Uri can either
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw, String fileName, Long fileSize, String batchId, Boolean batchLast, Boolean canResume, Boolean startOver, Boolean unzip, String tool, Boolean overwrite) throws InvalidOrMissingParameterException 	{
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Prepares the links for uploading files to the target Share.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* populated based on the upload method, provider, and resume parameters passed to the
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* upload call.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw", if the "Raw" parameter
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* was provided to the Uploader, or use MIME multi-part form encoding otherwise. Raw uploads
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* it indicates that the server has identified a partial upload with that specification, and is
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders: the result code for the HTTP POST calls to Chunk and Finish Uri can either
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw, String fileName, Long fileSize, String batchId, Boolean batchLast, Boolean canResume, Boolean startOver, Boolean unzip, String tool) throws InvalidOrMissingParameterException 	{
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Prepares the links for uploading files to the target Share.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* populated based on the upload method, provider, and resume parameters passed to the
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* upload call.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw", if the "Raw" parameter
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* was provided to the Uploader, or use MIME multi-part form encoding otherwise. Raw uploads
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* it indicates that the server has identified a partial upload with that specification, and is
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders: the result code for the HTTP POST calls to Chunk and Finish Uri can either
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw, String fileName, Long fileSize, String batchId, Boolean batchLast, Boolean canResume, Boolean startOver, Boolean unzip) throws InvalidOrMissingParameterException 	{
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Prepares the links for uploading files to the target Share.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* populated based on the upload method, provider, and resume parameters passed to the
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* upload call.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw", if the "Raw" parameter
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* was provided to the Uploader, or use MIME multi-part form encoding otherwise. Raw uploads
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* it indicates that the server has identified a partial upload with that specification, and is
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders: the result code for the HTTP POST calls to Chunk and Finish Uri can either
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw, String fileName, Long fileSize, String batchId, Boolean batchLast, Boolean canResume, Boolean startOver) throws InvalidOrMissingParameterException 	{
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Prepares the links for uploading files to the target Share.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* populated based on the upload method, provider, and resume parameters passed to the
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* upload call.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw", if the "Raw" parameter
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* was provided to the Uploader, or use MIME multi-part form encoding otherwise. Raw uploads
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* it indicates that the server has identified a partial upload with that specification, and is
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders: the result code for the HTTP POST calls to Chunk and Finish Uri can either
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw, String fileName, Long fileSize, String batchId, Boolean batchLast, Boolean canResume) throws InvalidOrMissingParameterException 	{
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Prepares the links for uploading files to the target Share.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* populated based on the upload method, provider, and resume parameters passed to the
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* upload call.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw", if the "Raw" parameter
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* was provided to the Uploader, or use MIME multi-part form encoding otherwise. Raw uploads
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* it indicates that the server has identified a partial upload with that specification, and is
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders: the result code for the HTTP POST calls to Chunk and Finish Uri can either
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw, String fileName, Long fileSize, String batchId, Boolean batchLast) throws InvalidOrMissingParameterException 	{
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Prepares the links for uploading files to the target Share.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* populated based on the upload method, provider, and resume parameters passed to the
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* upload call.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw", if the "Raw" parameter
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* was provided to the Uploader, or use MIME multi-part form encoding otherwise. Raw uploads
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* it indicates that the server has identified a partial upload with that specification, and is
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders: the result code for the HTTP POST calls to Chunk and Finish Uri can either
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw, String fileName, Long fileSize, String batchId) throws InvalidOrMissingParameterException 	{
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Prepares the links for uploading files to the target Share.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* populated based on the upload method, provider, and resume parameters passed to the
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* upload call.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw", if the "Raw" parameter
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* was provided to the Uploader, or use MIME multi-part form encoding otherwise. Raw uploads
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* it indicates that the server has identified a partial upload with that specification, and is
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders: the result code for the HTTP POST calls to Chunk and Finish Uri can either
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw, String fileName, Long fileSize) throws InvalidOrMissingParameterException 	{
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Prepares the links for uploading files to the target Share.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* populated based on the upload method, provider, and resume parameters passed to the
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* upload call.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw", if the "Raw" parameter
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* was provided to the Uploader, or use MIME multi-part form encoding otherwise. Raw uploads
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* it indicates that the server has identified a partial upload with that specification, and is
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders: the result code for the HTTP POST calls to Chunk and Finish Uri can either
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw, String fileName) throws InvalidOrMissingParameterException 	{
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Prepares the links for uploading files to the target Share.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* populated based on the upload method, provider, and resume parameters passed to the
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* upload call.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw", if the "Raw" parameter
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* was provided to the Uploader, or use MIME multi-part form encoding otherwise. Raw uploads
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* it indicates that the server has identified a partial upload with that specification, and is
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders: the result code for the HTTP POST calls to Chunk and Finish Uri can either
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw) throws InvalidOrMissingParameterException 	{
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Prepares the links for uploading files to the target Share.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* populated based on the upload method, provider, and resume parameters passed to the
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* upload call.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw", if the "Raw" parameter
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* was provided to the Uploader, or use MIME multi-part form encoding otherwise. Raw uploads
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* it indicates that the server has identified a partial upload with that specification, and is
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders: the result code for the HTTP POST calls to Chunk and Finish Uri can either
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method) throws InvalidOrMissingParameterException 	{
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Prepares the links for uploading files to the target Share.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* populated based on the upload method, provider, and resume parameters passed to the
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* upload call.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw", if the "Raw" parameter
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* was provided to the Uploader, or use MIME multi-part form encoding otherwise. Raw uploads
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* it indicates that the server has identified a partial upload with that specification, and is
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders: the result code for the HTTP POST calls to Chunk and Finish Uri can either
com\citrix\sharefile\api\entities\SFSharesEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
com\citrix\sharefile\api\entities\SFSharesEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url) throws InvalidOrMissingParameterException 	{
com\citrix\sharefile\api\entities\SFSharesEntity.java:	public ISFQuery<SFUploadSpecification> upload2(URI url, SFUploadRequestParams uploadParams, Integer expirationDays) throws InvalidOrMissingParameterException 	{
com\citrix\sharefile\api\entities\SFSharesEntity.java:		if (uploadParams == null) {
com\citrix\sharefile\api\entities\SFSharesEntity.java:			throw new InvalidOrMissingParameterException("uploadParams");
com\citrix\sharefile\api\entities\SFSharesEntity.java:		sfApiQuery.setBody(uploadParams);
com\citrix\sharefile\api\entities\SFSharesEntity.java:	public ISFQuery<SFUploadSpecification> upload2(URI url, SFUploadRequestParams uploadParams) throws InvalidOrMissingParameterException 	{
com\citrix\sharefile\api\entities\SFSharesEntity.java:		if (uploadParams == null) {
com\citrix\sharefile\api\entities\SFSharesEntity.java:			throw new InvalidOrMissingParameterException("uploadParams");
com\citrix\sharefile\api\entities\SFSharesEntity.java:		sfApiQuery.setBody(uploadParams);
com\citrix\sharefile\api\https\SFUploadRunnable.java:  "ChunkUri": "https://storage-ec2-34.sharefile.com/upload-streaming-2.aspx?batchid=723ffb79-d720-4de8-b95d-087be1e6462a&overwrite=true&uploadid=rsu-9c48c04a5fb84f9d8fc93875231b01ca&raw=1&encparams=phT2SuROQY1XrVtmjxwO2yRkHK2uBy1BtAjWhNYAu-lvRQr3eTm-Xh6zYbz3Lc9FfRoDvzBCdI7SyPDVrxL0bR9-cb7IsTFbIcnPRRJ8xLn0nJ0yxIeKXV-m-gb0HWzHGdHOnKTBEEgwD969n-8rbXu6jvkZ3UhEwY6I79GfdTogsf1vi7lFrfPrTe8TV5isPOPSpSINN3qxBI_qWJoy8D_AUnK009vuFHJP4t9yzPi6rDqmfU-7ZhmhncG4rsBfTdEWL3wQiOdU5kNnFl5WkSzjO8dg1vmjSidVSreUN_YJeQw95i8w5XaVA7BGuWDDNXjE8rV53cyQ9p2blo6Xovj4fxQi6wSf0J6CqLKZnFgbHTd7IVvexhdXhTMYAWce01eMBr7iWD9Kd2J3O_nLX3oEWKMDgqCg6SCSd8baO9_EBiQ8QnDwfh8tWeOQq60_gXeX-wBn_TAPNUPTmV1RyD5nt9sn5Q77Rd6YtiOiSjNI98z2mCTSiLp3TYMm4gB38CawObllVnJuWIERHKGbyEwJhE5PNxdMQC4PeM4$",
com\citrix\sharefile\api\https\SFUploadRunnable.java:			upload(); // upload
com\citrix\sharefile\api\https\SFUploadRunnable.java:			ISFQuery<SFUploadSpecification> uploadQuery = mApiClient.items().upload(new URI(mV3Url)
com\citrix\sharefile\api\https\SFUploadRunnable.java:            uploadQuery.setCredentials(mUsername,mPassword);
com\citrix\sharefile\api\https\SFUploadRunnable.java:            return mApiClient.executeQuery(uploadQuery);
com\citrix\sharefile\api\https\SFUploadRunnable.java:        SFUploadRequestParams uploadRequestParams = new SFUploadRequestParams();
com\citrix\sharefile\api\https\SFUploadRunnable.java:        uploadRequestParams.setFileName(fileName);
com\citrix\sharefile\api\https\SFUploadRunnable.java:        uploadRequestParams.setClientCreatedDate(now);
com\citrix\sharefile\api\https\SFUploadRunnable.java:        uploadRequestParams.setClientModifiedDate(now);
com\citrix\sharefile\api\https\SFUploadRunnable.java:        uploadRequestParams.setDetails(details);
com\citrix\sharefile\api\https\SFUploadRunnable.java:        uploadRequestParams.setFileSize(fileSize);
com\citrix\sharefile\api\https\SFUploadRunnable.java:        uploadRequestParams.setMethod(new SFSafeEnum<SFUploadMethod>(SFUploadMethod.Streamed));
com\citrix\sharefile\api\https\SFUploadRunnable.java:        uploadRequestParams.setOverwrite(true);
com\citrix\sharefile\api\https\SFUploadRunnable.java:        uploadRequestParams.setThreadCount(1);
com\citrix\sharefile\api\https\SFUploadRunnable.java:        uploadRequestParams.setTitle(fileName);
com\citrix\sharefile\api\https\SFUploadRunnable.java:        uploadRequestParams.setTool("SFV3JAVASDK");
com\citrix\sharefile\api\https\SFUploadRunnable.java:        uploadRequestParams.setRaw(true);
com\citrix\sharefile\api\https\SFUploadRunnable.java:        return uploadRequestParams;
com\citrix\sharefile\api\https\SFUploadRunnable.java:	 * Chunk upload response can be of json type sample:
com\citrix\sharefile\api\https\SFUploadRunnable.java:				Logger.e(TAG,"exception parsing upload response",e);
com\citrix\sharefile\api\https\SFUploadRunnable.java:				mErrorMessage = "exception parsing upload response";
com\citrix\sharefile\api\https\SFUploadRunnable.java:	 *   This tries to upload a chunk. Returns a detialed object with the httpErrorCode and the ChunkResponse from the server.
com\citrix\sharefile\api\https\SFUploadRunnable.java:	private long uploadChunk(byte[] fileChunk,int chunkLength,boolean isLast, MessageDigest md, long previousChunkTotal) throws SFSDKException
com\citrix\sharefile\api\https\SFUploadRunnable.java:	private void upload() throws SFSDKException
com\citrix\sharefile\api\https\SFUploadRunnable.java:                previousChunkTotalBytes += uploadChunk(fileChunk,chunkLength,isLast,md,previousChunkTotalBytes);
com\citrix\sharefile\api\https\SFUploadRunnable.java:	private void updateProgress(long uploadedBytes)
com\citrix\sharefile\api\https\SFUploadRunnable.java:			mProgressListener.bytesTransfered(uploadedBytes);
com\citrix\sharefile\api\interfaces\ISFApiClient.java:    public SFUploadRunnable getUploader(SFUploadRequestParams uploadRequestParams,
com\citrix\sharefile\api\models\SFAccessControl.java:		* Defines whether the principal can add files (upload) into the Item
com\citrix\sharefile\api\models\SFAccessControl.java:		* Defines whether the principal can add files (upload) into the Item
com\citrix\sharefile\api\models\SFAccessControl.java:	public void setCanUpload(Boolean canupload) {
com\citrix\sharefile\api\models\SFAccessControl.java:		this.CanUpload = canupload;
com\citrix\sharefile\api\models\SFAccessControl.java:		* Defines the notification preference for upload events. If set, the principal will receive
com\citrix\sharefile\api\models\SFAccessControl.java:		* notifications when new files are uploaded into this Item
com\citrix\sharefile\api\models\SFAccessControl.java:		* Defines the notification preference for upload events. If set, the principal will receive
com\citrix\sharefile\api\models\SFAccessControl.java:		* notifications when new files are uploaded into this Item
com\citrix\sharefile\api\models\SFAccessControl.java:	public void setNotifyOnUpload(Boolean notifyonupload) {
com\citrix\sharefile\api\models\SFAccessControl.java:		this.NotifyOnUpload = notifyonupload;
com\citrix\sharefile\api\models\SFAccountPreferences.java:	public void setEnableSelfNotificationsUpload(Boolean enableselfnotificationsupload) {
com\citrix\sharefile\api\models\SFAccountPreferences.java:		this.EnableSelfNotificationsUpload = enableselfnotificationsupload;
com\citrix\sharefile\api\models\SFAccountPreferences.java:	public void setEnableUploadShareIDReceipt(Boolean enableuploadshareidreceipt) {
com\citrix\sharefile\api\models\SFAccountPreferences.java:		this.EnableUploadShareIDReceipt = enableuploadshareidreceipt;
com\citrix\sharefile\api\models\SFAccountPreferences.java:	public void setShowDownloadLinkInUploadNotification(Boolean showdownloadlinkinuploadnotification) {
com\citrix\sharefile\api\models\SFAccountPreferences.java:		this.ShowDownloadLinkInUploadNotification = showdownloadlinkinuploadnotification;
com\citrix\sharefile\api\models\SFItemInfo.java:	public void setCanUpload(Boolean canupload) {
com\citrix\sharefile\api\models\SFItemInfo.java:		this.CanUpload = canupload;
com\citrix\sharefile\api\models\SFOutlookInformation.java:	public void setUploadInfoLevel(SFOutlookInformationOptionString uploadinfolevel) {
com\citrix\sharefile\api\models\SFOutlookInformation.java:		this.UploadInfoLevel = uploadinfolevel;
com\citrix\sharefile\api\models\SFOutlookInformation.java:	public void setNotifyOnUpload(SFOutlookInformationOptionBool notifyonupload) {
com\citrix\sharefile\api\models\SFOutlookInformation.java:		this.NotifyOnUpload = notifyonupload;
com\citrix\sharefile\api\models\SFShareRequestParams.java:	public void setNotifyOnUpload(Boolean notifyonupload) {
com\citrix\sharefile\api\models\SFShareRequestParams.java:		this.NotifyOnUpload = notifyonupload;
com\citrix\sharefile\api\models\SFUploadSpecification.java:		* The Upload method that must be used for this upload
com\citrix\sharefile\api\models\SFUploadSpecification.java:		* The Upload method that must be used for this upload
com\citrix\sharefile\api\models\SFUploadSpecification.java:		* If provided, clients must issue a request to this Uri before uploading any data.
com\citrix\sharefile\api\models\SFUploadSpecification.java:		* If provided, clients must issue a request to this Uri before uploading any data.
com\citrix\sharefile\api\models\SFUploadSpecification.java:		* If provided, specifies the final call the client must perform to finish the upload process
com\citrix\sharefile\api\models\SFUploadSpecification.java:		* If provided, specifies the final call the client must perform to finish the upload process
com\citrix\sharefile\api\models\SFUploadSpecification.java:		* Allows the client to check progress of standard uploads
com\citrix\sharefile\api\models\SFUploadSpecification.java:		* Allows the client to check progress of standard uploads
com\citrix\sharefile\api\models\SFUploadSpecification.java:		* Specifies a Resumable upload is supproted.
com\citrix\sharefile\api\models\SFUploadSpecification.java:		* Specifies a Resumable upload is supproted.
com\citrix\sharefile\api\models\SFUserPreferences.java:	public void setEnableFlashUpload(Boolean enableflashupload) {
com\citrix\sharefile\api\models\SFUserPreferences.java:		this.EnableFlashUpload = enableflashupload;
com\citrix\sharefile\api\models\SFUserPreferences.java:	public void setEnableJavaUpload(Boolean enablejavaupload) {
com\citrix\sharefile\api\models\SFUserPreferences.java:		this.EnableJavaUpload = enablejavaupload;
com\citrix\sharefile\api\models\SFUserPreferences.java:	public void setNotifyOnUploadByDefault(Boolean notifyonuploadbydefault) {
com\citrix\sharefile\api\models\SFUserPreferences.java:		this.NotifyOnUploadByDefault = notifyonuploadbydefault;
com\citrix\sharefile\api\SFApiClient.java:    public SFUploadRunnable getUploader(SFUploadRequestParams uploadRequestParams,
com\citrix\sharefile\api\SFApiClient.java:        return new SFUploadRunnable(uploadRequestParams.geturl().toString(), true,
com\citrix\sharefile\api\SFApiClient.java:                uploadRequestParams.getFileSize(),
com\citrix\sharefile\api\SFApiClient.java:                uploadRequestParams.getFileName(),
com\citrix\sharefile\api\SFApiClient.java:                null, null, uploadRequestParams.getDetails());
com\citrix\sharefile\api\SFApiClient.java:     * prepare runnable to be used to upload a file
com\citrix\sharefile\api\SFProvider.java:	 *  "https://szqatest2.sharefiletest.com/sp/upload-streaming-2.aspx?uploadid=rsu-27564a05c0cf4052989099f3e880afda&parentid
com\citrix\sharefile\api\SFProvider.java:        if(path == null || path.length() < 2 ) //we check this since the path should always contain /v3/ or /upload-streaming
com\citrix\sharefile\api\utils\Utils.java:		//Don't break the URI in components. On a certain ZK zones we are getting h-params during upload.
SFApiClient.java:import com.citrix.sharefile.api.https.upload.SFUploadRunnable;
SFApiClient.java:	public SFUploadRunnable getUploader(SFUploadRequestParams uploadRequestParams,
SFApiClient.java:		return new SFUploadRunnable(uploadRequestParams.geturl().toString(), true,
SFApiClient.java:				uploadRequestParams.getFileSize(),
SFApiClient.java:				uploadRequestParams.getFileName(),
SFApiClient.java:				null, null, uploadRequestParams.getDetails());
SFApiClient.java:	 * prepare runnable to be used to upload a file
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For example, when users upload or modify an existing file, a new Item
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For example, when users upload or modify an existing file, a new Item
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Prepares the links for uploading files to the target Folder.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* populated based on the upload method, provider, and canResume parameters passed to the
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload call.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* There are two different URLs for upload: /sf/v3/Items(id)/Upload accepts parameters
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* to retrieve the Item ID of the file after the upload is completed.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw" (if the parameter raw=true
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* is provided to the Uploader) or use MIME multi-part form encoding otherwise. Raw uploads
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For Streamed and Threaded uploads, if the CanResume parameter is specified in the call to Upload,
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload with that specification and is ready to resume the upload process. The client can
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* ResumeOffset. If the client decides to restart the upload, it should simply ignore the resume
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw, String fileName, Long fileSize, String batchId, Boolean batchLast, Boolean canResume, Boolean startOver, Boolean unzip, String tool, Boolean overwrite, String title, String details, Boolean isSend, String sendGuid, String opid, Integer threadCount, String responseFormat, Boolean notify, Date clientCreatedDateUTC, Date clientModifiedDateUTC, Integer expirationDays) throws InvalidOrMissingParameterException 	{
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Prepares the links for uploading files to the target Folder.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* populated based on the upload method, provider, and canResume parameters passed to the
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload call.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* There are two different URLs for upload: /sf/v3/Items(id)/Upload accepts parameters
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* to retrieve the Item ID of the file after the upload is completed.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw" (if the parameter raw=true
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* is provided to the Uploader) or use MIME multi-part form encoding otherwise. Raw uploads
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For Streamed and Threaded uploads, if the CanResume parameter is specified in the call to Upload,
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload with that specification and is ready to resume the upload process. The client can
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* ResumeOffset. If the client decides to restart the upload, it should simply ignore the resume
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw, String fileName, Long fileSize, String batchId, Boolean batchLast, Boolean canResume, Boolean startOver, Boolean unzip, String tool, Boolean overwrite, String title, String details, Boolean isSend, String sendGuid, String opid, Integer threadCount, String responseFormat, Boolean notify, Date clientCreatedDateUTC, Date clientModifiedDateUTC) throws InvalidOrMissingParameterException 	{
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Prepares the links for uploading files to the target Folder.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* populated based on the upload method, provider, and canResume parameters passed to the
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload call.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* There are two different URLs for upload: /sf/v3/Items(id)/Upload accepts parameters
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* to retrieve the Item ID of the file after the upload is completed.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw" (if the parameter raw=true
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* is provided to the Uploader) or use MIME multi-part form encoding otherwise. Raw uploads
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For Streamed and Threaded uploads, if the CanResume parameter is specified in the call to Upload,
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload with that specification and is ready to resume the upload process. The client can
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* ResumeOffset. If the client decides to restart the upload, it should simply ignore the resume
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw, String fileName, Long fileSize, String batchId, Boolean batchLast, Boolean canResume, Boolean startOver, Boolean unzip, String tool, Boolean overwrite, String title, String details, Boolean isSend, String sendGuid, String opid, Integer threadCount, String responseFormat, Boolean notify, Date clientCreatedDateUTC) throws InvalidOrMissingParameterException 	{
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Prepares the links for uploading files to the target Folder.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* populated based on the upload method, provider, and canResume parameters passed to the
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload call.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* There are two different URLs for upload: /sf/v3/Items(id)/Upload accepts parameters
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* to retrieve the Item ID of the file after the upload is completed.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw" (if the parameter raw=true
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* is provided to the Uploader) or use MIME multi-part form encoding otherwise. Raw uploads
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For Streamed and Threaded uploads, if the CanResume parameter is specified in the call to Upload,
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload with that specification and is ready to resume the upload process. The client can
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* ResumeOffset. If the client decides to restart the upload, it should simply ignore the resume
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw, String fileName, Long fileSize, String batchId, Boolean batchLast, Boolean canResume, Boolean startOver, Boolean unzip, String tool, Boolean overwrite, String title, String details, Boolean isSend, String sendGuid, String opid, Integer threadCount, String responseFormat, Boolean notify) throws InvalidOrMissingParameterException 	{
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Prepares the links for uploading files to the target Folder.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* populated based on the upload method, provider, and canResume parameters passed to the
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload call.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* There are two different URLs for upload: /sf/v3/Items(id)/Upload accepts parameters
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* to retrieve the Item ID of the file after the upload is completed.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw" (if the parameter raw=true
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* is provided to the Uploader) or use MIME multi-part form encoding otherwise. Raw uploads
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For Streamed and Threaded uploads, if the CanResume parameter is specified in the call to Upload,
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload with that specification and is ready to resume the upload process. The client can
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* ResumeOffset. If the client decides to restart the upload, it should simply ignore the resume
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw, String fileName, Long fileSize, String batchId, Boolean batchLast, Boolean canResume, Boolean startOver, Boolean unzip, String tool, Boolean overwrite, String title, String details, Boolean isSend, String sendGuid, String opid, Integer threadCount, String responseFormat) throws InvalidOrMissingParameterException 	{
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Prepares the links for uploading files to the target Folder.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* populated based on the upload method, provider, and canResume parameters passed to the
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload call.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* There are two different URLs for upload: /sf/v3/Items(id)/Upload accepts parameters
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* to retrieve the Item ID of the file after the upload is completed.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw" (if the parameter raw=true
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* is provided to the Uploader) or use MIME multi-part form encoding otherwise. Raw uploads
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For Streamed and Threaded uploads, if the CanResume parameter is specified in the call to Upload,
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload with that specification and is ready to resume the upload process. The client can
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* ResumeOffset. If the client decides to restart the upload, it should simply ignore the resume
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw, String fileName, Long fileSize, String batchId, Boolean batchLast, Boolean canResume, Boolean startOver, Boolean unzip, String tool, Boolean overwrite, String title, String details, Boolean isSend, String sendGuid, String opid, Integer threadCount) throws InvalidOrMissingParameterException 	{
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Prepares the links for uploading files to the target Folder.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* populated based on the upload method, provider, and canResume parameters passed to the
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload call.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* There are two different URLs for upload: /sf/v3/Items(id)/Upload accepts parameters
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* to retrieve the Item ID of the file after the upload is completed.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw" (if the parameter raw=true
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* is provided to the Uploader) or use MIME multi-part form encoding otherwise. Raw uploads
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For Streamed and Threaded uploads, if the CanResume parameter is specified in the call to Upload,
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload with that specification and is ready to resume the upload process. The client can
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* ResumeOffset. If the client decides to restart the upload, it should simply ignore the resume
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw, String fileName, Long fileSize, String batchId, Boolean batchLast, Boolean canResume, Boolean startOver, Boolean unzip, String tool, Boolean overwrite, String title, String details, Boolean isSend, String sendGuid, String opid) throws InvalidOrMissingParameterException 	{
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Prepares the links for uploading files to the target Folder.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* populated based on the upload method, provider, and canResume parameters passed to the
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload call.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* There are two different URLs for upload: /sf/v3/Items(id)/Upload accepts parameters
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* to retrieve the Item ID of the file after the upload is completed.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw" (if the parameter raw=true
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* is provided to the Uploader) or use MIME multi-part form encoding otherwise. Raw uploads
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For Streamed and Threaded uploads, if the CanResume parameter is specified in the call to Upload,
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload with that specification and is ready to resume the upload process. The client can
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* ResumeOffset. If the client decides to restart the upload, it should simply ignore the resume
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw, String fileName, Long fileSize, String batchId, Boolean batchLast, Boolean canResume, Boolean startOver, Boolean unzip, String tool, Boolean overwrite, String title, String details, Boolean isSend, String sendGuid) throws InvalidOrMissingParameterException 	{
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Prepares the links for uploading files to the target Folder.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* populated based on the upload method, provider, and canResume parameters passed to the
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload call.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* There are two different URLs for upload: /sf/v3/Items(id)/Upload accepts parameters
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* to retrieve the Item ID of the file after the upload is completed.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw" (if the parameter raw=true
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* is provided to the Uploader) or use MIME multi-part form encoding otherwise. Raw uploads
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For Streamed and Threaded uploads, if the CanResume parameter is specified in the call to Upload,
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload with that specification and is ready to resume the upload process. The client can
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* ResumeOffset. If the client decides to restart the upload, it should simply ignore the resume
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw, String fileName, Long fileSize, String batchId, Boolean batchLast, Boolean canResume, Boolean startOver, Boolean unzip, String tool, Boolean overwrite, String title, String details, Boolean isSend) throws InvalidOrMissingParameterException 	{
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Prepares the links for uploading files to the target Folder.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* populated based on the upload method, provider, and canResume parameters passed to the
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload call.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* There are two different URLs for upload: /sf/v3/Items(id)/Upload accepts parameters
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* to retrieve the Item ID of the file after the upload is completed.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw" (if the parameter raw=true
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* is provided to the Uploader) or use MIME multi-part form encoding otherwise. Raw uploads
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For Streamed and Threaded uploads, if the CanResume parameter is specified in the call to Upload,
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload with that specification and is ready to resume the upload process. The client can
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* ResumeOffset. If the client decides to restart the upload, it should simply ignore the resume
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw, String fileName, Long fileSize, String batchId, Boolean batchLast, Boolean canResume, Boolean startOver, Boolean unzip, String tool, Boolean overwrite, String title, String details) throws InvalidOrMissingParameterException 	{
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Prepares the links for uploading files to the target Folder.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* populated based on the upload method, provider, and canResume parameters passed to the
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload call.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* There are two different URLs for upload: /sf/v3/Items(id)/Upload accepts parameters
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* to retrieve the Item ID of the file after the upload is completed.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw" (if the parameter raw=true
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* is provided to the Uploader) or use MIME multi-part form encoding otherwise. Raw uploads
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For Streamed and Threaded uploads, if the CanResume parameter is specified in the call to Upload,
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload with that specification and is ready to resume the upload process. The client can
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* ResumeOffset. If the client decides to restart the upload, it should simply ignore the resume
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw, String fileName, Long fileSize, String batchId, Boolean batchLast, Boolean canResume, Boolean startOver, Boolean unzip, String tool, Boolean overwrite, String title) throws InvalidOrMissingParameterException 	{
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Prepares the links for uploading files to the target Folder.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* populated based on the upload method, provider, and canResume parameters passed to the
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload call.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* There are two different URLs for upload: /sf/v3/Items(id)/Upload accepts parameters
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* to retrieve the Item ID of the file after the upload is completed.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw" (if the parameter raw=true
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* is provided to the Uploader) or use MIME multi-part form encoding otherwise. Raw uploads
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For Streamed and Threaded uploads, if the CanResume parameter is specified in the call to Upload,
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload with that specification and is ready to resume the upload process. The client can
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* ResumeOffset. If the client decides to restart the upload, it should simply ignore the resume
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw, String fileName, Long fileSize, String batchId, Boolean batchLast, Boolean canResume, Boolean startOver, Boolean unzip, String tool, Boolean overwrite) throws InvalidOrMissingParameterException 	{
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Prepares the links for uploading files to the target Folder.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* populated based on the upload method, provider, and canResume parameters passed to the
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload call.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* There are two different URLs for upload: /sf/v3/Items(id)/Upload accepts parameters
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* to retrieve the Item ID of the file after the upload is completed.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw" (if the parameter raw=true
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* is provided to the Uploader) or use MIME multi-part form encoding otherwise. Raw uploads
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For Streamed and Threaded uploads, if the CanResume parameter is specified in the call to Upload,
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload with that specification and is ready to resume the upload process. The client can
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* ResumeOffset. If the client decides to restart the upload, it should simply ignore the resume
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw, String fileName, Long fileSize, String batchId, Boolean batchLast, Boolean canResume, Boolean startOver, Boolean unzip, String tool) throws InvalidOrMissingParameterException 	{
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Prepares the links for uploading files to the target Folder.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* populated based on the upload method, provider, and canResume parameters passed to the
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload call.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* There are two different URLs for upload: /sf/v3/Items(id)/Upload accepts parameters
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* to retrieve the Item ID of the file after the upload is completed.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw" (if the parameter raw=true
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* is provided to the Uploader) or use MIME multi-part form encoding otherwise. Raw uploads
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For Streamed and Threaded uploads, if the CanResume parameter is specified in the call to Upload,
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload with that specification and is ready to resume the upload process. The client can
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* ResumeOffset. If the client decides to restart the upload, it should simply ignore the resume
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw, String fileName, Long fileSize, String batchId, Boolean batchLast, Boolean canResume, Boolean startOver, Boolean unzip) throws InvalidOrMissingParameterException 	{
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Prepares the links for uploading files to the target Folder.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* populated based on the upload method, provider, and canResume parameters passed to the
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload call.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* There are two different URLs for upload: /sf/v3/Items(id)/Upload accepts parameters
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* to retrieve the Item ID of the file after the upload is completed.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw" (if the parameter raw=true
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* is provided to the Uploader) or use MIME multi-part form encoding otherwise. Raw uploads
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For Streamed and Threaded uploads, if the CanResume parameter is specified in the call to Upload,
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload with that specification and is ready to resume the upload process. The client can
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* ResumeOffset. If the client decides to restart the upload, it should simply ignore the resume
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw, String fileName, Long fileSize, String batchId, Boolean batchLast, Boolean canResume, Boolean startOver) throws InvalidOrMissingParameterException 	{
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Prepares the links for uploading files to the target Folder.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* populated based on the upload method, provider, and canResume parameters passed to the
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload call.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* There are two different URLs for upload: /sf/v3/Items(id)/Upload accepts parameters
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* to retrieve the Item ID of the file after the upload is completed.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw" (if the parameter raw=true
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* is provided to the Uploader) or use MIME multi-part form encoding otherwise. Raw uploads
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For Streamed and Threaded uploads, if the CanResume parameter is specified in the call to Upload,
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload with that specification and is ready to resume the upload process. The client can
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* ResumeOffset. If the client decides to restart the upload, it should simply ignore the resume
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw, String fileName, Long fileSize, String batchId, Boolean batchLast, Boolean canResume) throws InvalidOrMissingParameterException 	{
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Prepares the links for uploading files to the target Folder.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* populated based on the upload method, provider, and canResume parameters passed to the
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload call.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* There are two different URLs for upload: /sf/v3/Items(id)/Upload accepts parameters
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* to retrieve the Item ID of the file after the upload is completed.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw" (if the parameter raw=true
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* is provided to the Uploader) or use MIME multi-part form encoding otherwise. Raw uploads
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For Streamed and Threaded uploads, if the CanResume parameter is specified in the call to Upload,
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload with that specification and is ready to resume the upload process. The client can
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* ResumeOffset. If the client decides to restart the upload, it should simply ignore the resume
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw, String fileName, Long fileSize, String batchId, Boolean batchLast) throws InvalidOrMissingParameterException 	{
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Prepares the links for uploading files to the target Folder.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* populated based on the upload method, provider, and canResume parameters passed to the
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload call.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* There are two different URLs for upload: /sf/v3/Items(id)/Upload accepts parameters
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* to retrieve the Item ID of the file after the upload is completed.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw" (if the parameter raw=true
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* is provided to the Uploader) or use MIME multi-part form encoding otherwise. Raw uploads
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For Streamed and Threaded uploads, if the CanResume parameter is specified in the call to Upload,
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload with that specification and is ready to resume the upload process. The client can
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* ResumeOffset. If the client decides to restart the upload, it should simply ignore the resume
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw, String fileName, Long fileSize, String batchId) throws InvalidOrMissingParameterException 	{
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Prepares the links for uploading files to the target Folder.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* populated based on the upload method, provider, and canResume parameters passed to the
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload call.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* There are two different URLs for upload: /sf/v3/Items(id)/Upload accepts parameters
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* to retrieve the Item ID of the file after the upload is completed.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw" (if the parameter raw=true
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* is provided to the Uploader) or use MIME multi-part form encoding otherwise. Raw uploads
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For Streamed and Threaded uploads, if the CanResume parameter is specified in the call to Upload,
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload with that specification and is ready to resume the upload process. The client can
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* ResumeOffset. If the client decides to restart the upload, it should simply ignore the resume
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw, String fileName, Long fileSize) throws InvalidOrMissingParameterException 	{
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Prepares the links for uploading files to the target Folder.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* populated based on the upload method, provider, and canResume parameters passed to the
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload call.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* There are two different URLs for upload: /sf/v3/Items(id)/Upload accepts parameters
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* to retrieve the Item ID of the file after the upload is completed.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw" (if the parameter raw=true
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* is provided to the Uploader) or use MIME multi-part form encoding otherwise. Raw uploads
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For Streamed and Threaded uploads, if the CanResume parameter is specified in the call to Upload,
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload with that specification and is ready to resume the upload process. The client can
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* ResumeOffset. If the client decides to restart the upload, it should simply ignore the resume
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw, String fileName) throws InvalidOrMissingParameterException 	{
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Prepares the links for uploading files to the target Folder.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* populated based on the upload method, provider, and canResume parameters passed to the
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload call.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* There are two different URLs for upload: /sf/v3/Items(id)/Upload accepts parameters
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* to retrieve the Item ID of the file after the upload is completed.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw" (if the parameter raw=true
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* is provided to the Uploader) or use MIME multi-part form encoding otherwise. Raw uploads
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For Streamed and Threaded uploads, if the CanResume parameter is specified in the call to Upload,
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload with that specification and is ready to resume the upload process. The client can
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* ResumeOffset. If the client decides to restart the upload, it should simply ignore the resume
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw) throws InvalidOrMissingParameterException 	{
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Prepares the links for uploading files to the target Folder.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* populated based on the upload method, provider, and canResume parameters passed to the
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload call.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* There are two different URLs for upload: /sf/v3/Items(id)/Upload accepts parameters
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* to retrieve the Item ID of the file after the upload is completed.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw" (if the parameter raw=true
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* is provided to the Uploader) or use MIME multi-part form encoding otherwise. Raw uploads
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For Streamed and Threaded uploads, if the CanResume parameter is specified in the call to Upload,
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload with that specification and is ready to resume the upload process. The client can
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* ResumeOffset. If the client decides to restart the upload, it should simply ignore the resume
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method) throws InvalidOrMissingParameterException 	{
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Prepares the links for uploading files to the target Folder.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* populated based on the upload method, provider, and canResume parameters passed to the
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload call.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* There are two different URLs for upload: /sf/v3/Items(id)/Upload accepts parameters
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. For each call, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* the end of ChunkUri, as explained for Streamed uploads. After all chunks are sent, the client
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* to retrieve the Item ID of the file after the upload is completed.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw" (if the parameter raw=true
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* is provided to the Uploader) or use MIME multi-part form encoding otherwise. Raw uploads
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For Streamed and Threaded uploads, if the CanResume parameter is specified in the call to Upload,
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* upload with that specification and is ready to resume the upload process. The client can
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* ResumeOffset. If the client decides to restart the upload, it should simply ignore the resume
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* For all upload methods, successful HTTP POST calls to ChunkUri and FinishUri will return response
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url) throws InvalidOrMissingParameterException 	{
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	public ISFQuery<SFUploadSpecification> upload2(URI url, SFUploadRequestParams uploadParams, Integer expirationDays) throws InvalidOrMissingParameterException 	{
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:		if (uploadParams == null) {
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:			throw new InvalidOrMissingParameterException("uploadParams");
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:		sfApiQuery.setBody(uploadParams);
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:	public ISFQuery<SFUploadSpecification> upload2(URI url, SFUploadRequestParams uploadParams) throws InvalidOrMissingParameterException 	{
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:		if (uploadParams == null) {
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:			throw new InvalidOrMissingParameterException("uploadParams");
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFItemsEntity.java:		sfApiQuery.setBody(uploadParams);
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFRemoteUploadsEntity.java:	public ISFQuery<SFUploadSpecification> upload2(URI url, SFRemoteUploadRequestParams uploadParams, String userId, Integer expirationDays) throws InvalidOrMissingParameterException 	{
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFRemoteUploadsEntity.java:		if (uploadParams == null) {
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFRemoteUploadsEntity.java:			throw new InvalidOrMissingParameterException("uploadParams");
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFRemoteUploadsEntity.java:		sfApiQuery.setBody(uploadParams);
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFRemoteUploadsEntity.java:	public ISFQuery<SFUploadSpecification> upload2(URI url, SFRemoteUploadRequestParams uploadParams, String userId) throws InvalidOrMissingParameterException 	{
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFRemoteUploadsEntity.java:		if (uploadParams == null) {
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFRemoteUploadsEntity.java:			throw new InvalidOrMissingParameterException("uploadParams");
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFRemoteUploadsEntity.java:		sfApiQuery.setBody(uploadParams);
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Sends an Email to the specified list of addresses, containing a link to files upload.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Sends an Email to the specified list of addresses, containing a link to a download or an upload.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Prepares the links for uploading files to the target Share.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* populated based on the upload method, provider, and resume parameters passed to the
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* upload call.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw", if the "Raw" parameter
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* was provided to the Uploader, or use MIME multi-part form encoding otherwise. Raw uploads
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* it indicates that the server has identified a partial upload with that specification, and is
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders: the result code for the HTTP POST calls to Chunk and Finish Uri can either
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw, String fileName, Long fileSize, String batchId, Boolean batchLast, Boolean canResume, Boolean startOver, Boolean unzip, String tool, Boolean overwrite, String title, String details, Boolean isSend, String sendGuid, String opid, Integer threadCount, String responseFormat, Boolean notify, Date clientCreatedDateUTC, Date clientModifiedDateUTC, Integer expirationDays) throws InvalidOrMissingParameterException 	{
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Prepares the links for uploading files to the target Share.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* populated based on the upload method, provider, and resume parameters passed to the
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* upload call.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw", if the "Raw" parameter
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* was provided to the Uploader, or use MIME multi-part form encoding otherwise. Raw uploads
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* it indicates that the server has identified a partial upload with that specification, and is
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders: the result code for the HTTP POST calls to Chunk and Finish Uri can either
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw, String fileName, Long fileSize, String batchId, Boolean batchLast, Boolean canResume, Boolean startOver, Boolean unzip, String tool, Boolean overwrite, String title, String details, Boolean isSend, String sendGuid, String opid, Integer threadCount, String responseFormat, Boolean notify, Date clientCreatedDateUTC, Date clientModifiedDateUTC) throws InvalidOrMissingParameterException 	{
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Prepares the links for uploading files to the target Share.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* populated based on the upload method, provider, and resume parameters passed to the
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* upload call.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw", if the "Raw" parameter
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* was provided to the Uploader, or use MIME multi-part form encoding otherwise. Raw uploads
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* it indicates that the server has identified a partial upload with that specification, and is
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders: the result code for the HTTP POST calls to Chunk and Finish Uri can either
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw, String fileName, Long fileSize, String batchId, Boolean batchLast, Boolean canResume, Boolean startOver, Boolean unzip, String tool, Boolean overwrite, String title, String details, Boolean isSend, String sendGuid, String opid, Integer threadCount, String responseFormat, Boolean notify, Date clientCreatedDateUTC) throws InvalidOrMissingParameterException 	{
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Prepares the links for uploading files to the target Share.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* populated based on the upload method, provider, and resume parameters passed to the
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* upload call.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw", if the "Raw" parameter
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* was provided to the Uploader, or use MIME multi-part form encoding otherwise. Raw uploads
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* it indicates that the server has identified a partial upload with that specification, and is
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders: the result code for the HTTP POST calls to Chunk and Finish Uri can either
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw, String fileName, Long fileSize, String batchId, Boolean batchLast, Boolean canResume, Boolean startOver, Boolean unzip, String tool, Boolean overwrite, String title, String details, Boolean isSend, String sendGuid, String opid, Integer threadCount, String responseFormat, Boolean notify) throws InvalidOrMissingParameterException 	{
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Prepares the links for uploading files to the target Share.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* populated based on the upload method, provider, and resume parameters passed to the
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* upload call.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw", if the "Raw" parameter
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* was provided to the Uploader, or use MIME multi-part form encoding otherwise. Raw uploads
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* it indicates that the server has identified a partial upload with that specification, and is
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders: the result code for the HTTP POST calls to Chunk and Finish Uri can either
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw, String fileName, Long fileSize, String batchId, Boolean batchLast, Boolean canResume, Boolean startOver, Boolean unzip, String tool, Boolean overwrite, String title, String details, Boolean isSend, String sendGuid, String opid, Integer threadCount, String responseFormat) throws InvalidOrMissingParameterException 	{
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Prepares the links for uploading files to the target Share.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* populated based on the upload method, provider, and resume parameters passed to the
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* upload call.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw", if the "Raw" parameter
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* was provided to the Uploader, or use MIME multi-part form encoding otherwise. Raw uploads
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* it indicates that the server has identified a partial upload with that specification, and is
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders: the result code for the HTTP POST calls to Chunk and Finish Uri can either
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw, String fileName, Long fileSize, String batchId, Boolean batchLast, Boolean canResume, Boolean startOver, Boolean unzip, String tool, Boolean overwrite, String title, String details, Boolean isSend, String sendGuid, String opid, Integer threadCount) throws InvalidOrMissingParameterException 	{
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Prepares the links for uploading files to the target Share.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* populated based on the upload method, provider, and resume parameters passed to the
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* upload call.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw", if the "Raw" parameter
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* was provided to the Uploader, or use MIME multi-part form encoding otherwise. Raw uploads
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* it indicates that the server has identified a partial upload with that specification, and is
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders: the result code for the HTTP POST calls to Chunk and Finish Uri can either
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw, String fileName, Long fileSize, String batchId, Boolean batchLast, Boolean canResume, Boolean startOver, Boolean unzip, String tool, Boolean overwrite, String title, String details, Boolean isSend, String sendGuid, String opid) throws InvalidOrMissingParameterException 	{
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Prepares the links for uploading files to the target Share.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* populated based on the upload method, provider, and resume parameters passed to the
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* upload call.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw", if the "Raw" parameter
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* was provided to the Uploader, or use MIME multi-part form encoding otherwise. Raw uploads
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* it indicates that the server has identified a partial upload with that specification, and is
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders: the result code for the HTTP POST calls to Chunk and Finish Uri can either
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw, String fileName, Long fileSize, String batchId, Boolean batchLast, Boolean canResume, Boolean startOver, Boolean unzip, String tool, Boolean overwrite, String title, String details, Boolean isSend, String sendGuid) throws InvalidOrMissingParameterException 	{
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Prepares the links for uploading files to the target Share.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* populated based on the upload method, provider, and resume parameters passed to the
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* upload call.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw", if the "Raw" parameter
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* was provided to the Uploader, or use MIME multi-part form encoding otherwise. Raw uploads
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* it indicates that the server has identified a partial upload with that specification, and is
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders: the result code for the HTTP POST calls to Chunk and Finish Uri can either
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw, String fileName, Long fileSize, String batchId, Boolean batchLast, Boolean canResume, Boolean startOver, Boolean unzip, String tool, Boolean overwrite, String title, String details, Boolean isSend) throws InvalidOrMissingParameterException 	{
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Prepares the links for uploading files to the target Share.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* populated based on the upload method, provider, and resume parameters passed to the
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* upload call.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw", if the "Raw" parameter
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* was provided to the Uploader, or use MIME multi-part form encoding otherwise. Raw uploads
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* it indicates that the server has identified a partial upload with that specification, and is
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders: the result code for the HTTP POST calls to Chunk and Finish Uri can either
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw, String fileName, Long fileSize, String batchId, Boolean batchLast, Boolean canResume, Boolean startOver, Boolean unzip, String tool, Boolean overwrite, String title, String details) throws InvalidOrMissingParameterException 	{
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Prepares the links for uploading files to the target Share.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* populated based on the upload method, provider, and resume parameters passed to the
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* upload call.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw", if the "Raw" parameter
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* was provided to the Uploader, or use MIME multi-part form encoding otherwise. Raw uploads
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* it indicates that the server has identified a partial upload with that specification, and is
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders: the result code for the HTTP POST calls to Chunk and Finish Uri can either
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw, String fileName, Long fileSize, String batchId, Boolean batchLast, Boolean canResume, Boolean startOver, Boolean unzip, String tool, Boolean overwrite, String title) throws InvalidOrMissingParameterException 	{
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Prepares the links for uploading files to the target Share.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* populated based on the upload method, provider, and resume parameters passed to the
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* upload call.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw", if the "Raw" parameter
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* was provided to the Uploader, or use MIME multi-part form encoding otherwise. Raw uploads
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* it indicates that the server has identified a partial upload with that specification, and is
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders: the result code for the HTTP POST calls to Chunk and Finish Uri can either
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw, String fileName, Long fileSize, String batchId, Boolean batchLast, Boolean canResume, Boolean startOver, Boolean unzip, String tool, Boolean overwrite) throws InvalidOrMissingParameterException 	{
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Prepares the links for uploading files to the target Share.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* populated based on the upload method, provider, and resume parameters passed to the
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* upload call.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw", if the "Raw" parameter
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* was provided to the Uploader, or use MIME multi-part form encoding otherwise. Raw uploads
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* it indicates that the server has identified a partial upload with that specification, and is
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders: the result code for the HTTP POST calls to Chunk and Finish Uri can either
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw, String fileName, Long fileSize, String batchId, Boolean batchLast, Boolean canResume, Boolean startOver, Boolean unzip, String tool) throws InvalidOrMissingParameterException 	{
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Prepares the links for uploading files to the target Share.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* populated based on the upload method, provider, and resume parameters passed to the
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* upload call.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw", if the "Raw" parameter
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* was provided to the Uploader, or use MIME multi-part form encoding otherwise. Raw uploads
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* it indicates that the server has identified a partial upload with that specification, and is
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders: the result code for the HTTP POST calls to Chunk and Finish Uri can either
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw, String fileName, Long fileSize, String batchId, Boolean batchLast, Boolean canResume, Boolean startOver, Boolean unzip) throws InvalidOrMissingParameterException 	{
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Prepares the links for uploading files to the target Share.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* populated based on the upload method, provider, and resume parameters passed to the
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* upload call.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw", if the "Raw" parameter
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* was provided to the Uploader, or use MIME multi-part form encoding otherwise. Raw uploads
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* it indicates that the server has identified a partial upload with that specification, and is
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders: the result code for the HTTP POST calls to Chunk and Finish Uri can either
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw, String fileName, Long fileSize, String batchId, Boolean batchLast, Boolean canResume, Boolean startOver) throws InvalidOrMissingParameterException 	{
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Prepares the links for uploading files to the target Share.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* populated based on the upload method, provider, and resume parameters passed to the
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* upload call.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw", if the "Raw" parameter
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* was provided to the Uploader, or use MIME multi-part form encoding otherwise. Raw uploads
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* it indicates that the server has identified a partial upload with that specification, and is
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders: the result code for the HTTP POST calls to Chunk and Finish Uri can either
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw, String fileName, Long fileSize, String batchId, Boolean batchLast, Boolean canResume) throws InvalidOrMissingParameterException 	{
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Prepares the links for uploading files to the target Share.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* populated based on the upload method, provider, and resume parameters passed to the
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* upload call.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw", if the "Raw" parameter
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* was provided to the Uploader, or use MIME multi-part form encoding otherwise. Raw uploads
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* it indicates that the server has identified a partial upload with that specification, and is
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders: the result code for the HTTP POST calls to Chunk and Finish Uri can either
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw, String fileName, Long fileSize, String batchId, Boolean batchLast) throws InvalidOrMissingParameterException 	{
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Prepares the links for uploading files to the target Share.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* populated based on the upload method, provider, and resume parameters passed to the
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* upload call.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw", if the "Raw" parameter
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* was provided to the Uploader, or use MIME multi-part form encoding otherwise. Raw uploads
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* it indicates that the server has identified a partial upload with that specification, and is
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders: the result code for the HTTP POST calls to Chunk and Finish Uri can either
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw, String fileName, Long fileSize, String batchId) throws InvalidOrMissingParameterException 	{
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Prepares the links for uploading files to the target Share.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* populated based on the upload method, provider, and resume parameters passed to the
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* upload call.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw", if the "Raw" parameter
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* was provided to the Uploader, or use MIME multi-part form encoding otherwise. Raw uploads
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* it indicates that the server has identified a partial upload with that specification, and is
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders: the result code for the HTTP POST calls to Chunk and Finish Uri can either
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw, String fileName, Long fileSize) throws InvalidOrMissingParameterException 	{
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Prepares the links for uploading files to the target Share.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* populated based on the upload method, provider, and resume parameters passed to the
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* upload call.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw", if the "Raw" parameter
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* was provided to the Uploader, or use MIME multi-part form encoding otherwise. Raw uploads
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* it indicates that the server has identified a partial upload with that specification, and is
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders: the result code for the HTTP POST calls to Chunk and Finish Uri can either
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw, String fileName) throws InvalidOrMissingParameterException 	{
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Prepares the links for uploading files to the target Share.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* populated based on the upload method, provider, and resume parameters passed to the
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* upload call.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw", if the "Raw" parameter
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* was provided to the Uploader, or use MIME multi-part form encoding otherwise. Raw uploads
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* it indicates that the server has identified a partial upload with that specification, and is
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders: the result code for the HTTP POST calls to Chunk and Finish Uri can either
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method, Boolean raw) throws InvalidOrMissingParameterException 	{
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Prepares the links for uploading files to the target Share.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* populated based on the upload method, provider, and resume parameters passed to the
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* upload call.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw", if the "Raw" parameter
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* was provided to the Uploader, or use MIME multi-part form encoding otherwise. Raw uploads
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* it indicates that the server has identified a partial upload with that specification, and is
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders: the result code for the HTTP POST calls to Chunk and Finish Uri can either
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url, SFSafeEnum<SFUploadMethod> method) throws InvalidOrMissingParameterException 	{
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Prepares the links for uploading files to the target Share.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* populated based on the upload method, provider, and resume parameters passed to the
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* upload call.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Standard uploads use a single HTTP POST message to the ChunkUri address provided in
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* the response. All other fields will be empty. Standard uploads do not support Resume.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Streamed uploads use multiple HTTP POST calls to the ChunkUri address. The client must
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* Threaded uploads use multiple HTTP POST calls to ChunkUri, and can have a number of
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders, the contents of the POST Body can either be "raw", if the "Raw" parameter
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* was provided to the Uploader, or use MIME multi-part form encoding otherwise. Raw uploads
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* it indicates that the server has identified a partial upload with that specification, and is
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* For all uploaders: the result code for the HTTP POST calls to Chunk and Finish Uri can either
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	* @return an Upload Specification element, containing the links for uploading, and the parameters for resume. The caller must know the protocol for sending the prepare, chunk and finish URLs returned in the spec; as well as negotiate the resume upload.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	public ISFQuery<SFUploadSpecification> upload(URI url) throws InvalidOrMissingParameterException 	{
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	public ISFQuery<SFUploadSpecification> upload2(URI url, SFUploadRequestParams uploadParams, Integer expirationDays) throws InvalidOrMissingParameterException 	{
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:		if (uploadParams == null) {
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:			throw new InvalidOrMissingParameterException("uploadParams");
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:		sfApiQuery.setBody(uploadParams);
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:	public ISFQuery<SFUploadSpecification> upload2(URI url, SFUploadRequestParams uploadParams) throws InvalidOrMissingParameterException 	{
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:		if (uploadParams == null) {
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:			throw new InvalidOrMissingParameterException("uploadParams");
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\entities\SFSharesEntity.java:		sfApiQuery.setBody(uploadParams);
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\https\SFUploadRunnable.java:  "ChunkUri": "https://storage-ec2-34.sharefile.com/upload-streaming-2.aspx?batchid=723ffb79-d720-4de8-b95d-087be1e6462a&overwrite=true&uploadid=rsu-9c48c04a5fb84f9d8fc93875231b01ca&raw=1&encparams=phT2SuROQY1XrVtmjxwO2yRkHK2uBy1BtAjWhNYAu-lvRQr3eTm-Xh6zYbz3Lc9FfRoDvzBCdI7SyPDVrxL0bR9-cb7IsTFbIcnPRRJ8xLn0nJ0yxIeKXV-m-gb0HWzHGdHOnKTBEEgwD969n-8rbXu6jvkZ3UhEwY6I79GfdTogsf1vi7lFrfPrTe8TV5isPOPSpSINN3qxBI_qWJoy8D_AUnK009vuFHJP4t9yzPi6rDqmfU-7ZhmhncG4rsBfTdEWL3wQiOdU5kNnFl5WkSzjO8dg1vmjSidVSreUN_YJeQw95i8w5XaVA7BGuWDDNXjE8rV53cyQ9p2blo6Xovj4fxQi6wSf0J6CqLKZnFgbHTd7IVvexhdXhTMYAWce01eMBr7iWD9Kd2J3O_nLX3oEWKMDgqCg6SCSd8baO9_EBiQ8QnDwfh8tWeOQq60_gXeX-wBn_TAPNUPTmV1RyD5nt9sn5Q77Rd6YtiOiSjNI98z2mCTSiLp3TYMm4gB38CawObllVnJuWIERHKGbyEwJhE5PNxdMQC4PeM4$",
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\https\SFUploadRunnable.java:			upload(); // upload
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\https\SFUploadRunnable.java:			ISFQuery<SFUploadSpecification> uploadQuery = mApiClient.items().upload(new URI(mV3Url)
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\https\SFUploadRunnable.java:            uploadQuery.setCredentials(mUsername,mPassword);
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\https\SFUploadRunnable.java:            return mApiClient.executeQuery(uploadQuery);
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\https\SFUploadRunnable.java:        SFUploadRequestParams uploadRequestParams = new SFUploadRequestParams();
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\https\SFUploadRunnable.java:        uploadRequestParams.setFileName(fileName);
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\https\SFUploadRunnable.java:        uploadRequestParams.setClientCreatedDate(now);
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\https\SFUploadRunnable.java:        uploadRequestParams.setClientModifiedDate(now);
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\https\SFUploadRunnable.java:        uploadRequestParams.setDetails(details);
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\https\SFUploadRunnable.java:        uploadRequestParams.setFileSize(fileSize);
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\https\SFUploadRunnable.java:        uploadRequestParams.setMethod(new SFSafeEnum<SFUploadMethod>(SFUploadMethod.Streamed));
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\https\SFUploadRunnable.java:        uploadRequestParams.setOverwrite(true);
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\https\SFUploadRunnable.java:        uploadRequestParams.setThreadCount(1);
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\https\SFUploadRunnable.java:        uploadRequestParams.setTitle(fileName);
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\https\SFUploadRunnable.java:        uploadRequestParams.setTool("SFV3JAVASDK");
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\https\SFUploadRunnable.java:        uploadRequestParams.setRaw(true);
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\https\SFUploadRunnable.java:        return uploadRequestParams;
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\https\SFUploadRunnable.java:	 * Chunk upload response can be of json type sample:
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\https\SFUploadRunnable.java:				Logger.e(TAG,"exception parsing upload response",e);
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\https\SFUploadRunnable.java:				mErrorMessage = "exception parsing upload response";
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\https\SFUploadRunnable.java:	 *   This tries to upload a chunk. Returns a detialed object with the httpErrorCode and the ChunkResponse from the server.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\https\SFUploadRunnable.java:	private long uploadChunk(byte[] fileChunk,int chunkLength,boolean isLast, MessageDigest md, long previousChunkTotal) throws SFSDKException
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\https\SFUploadRunnable.java:	private void upload() throws SFSDKException
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\https\SFUploadRunnable.java:                previousChunkTotalBytes += uploadChunk(fileChunk,chunkLength,isLast,md,previousChunkTotalBytes);
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\https\SFUploadRunnable.java:	private void updateProgress(long uploadedBytes)
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\https\SFUploadRunnable.java:			mProgressListener.bytesTransfered(uploadedBytes);
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\interfaces\ISFApiClient.java:    public SFUploadRunnable getUploader(SFUploadRequestParams uploadRequestParams,
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\models\SFAccessControl.java:		* Defines whether the principal can add files (upload) into the Item
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\models\SFAccessControl.java:		* Defines whether the principal can add files (upload) into the Item
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\models\SFAccessControl.java:	public void setCanUpload(Boolean canupload) {
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\models\SFAccessControl.java:		this.CanUpload = canupload;
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\models\SFAccessControl.java:		* Defines the notification preference for upload events. If set, the principal will receive
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\models\SFAccessControl.java:		* notifications when new files are uploaded into this Item
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\models\SFAccessControl.java:		* Defines the notification preference for upload events. If set, the principal will receive
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\models\SFAccessControl.java:		* notifications when new files are uploaded into this Item
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\models\SFAccessControl.java:	public void setNotifyOnUpload(Boolean notifyonupload) {
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\models\SFAccessControl.java:		this.NotifyOnUpload = notifyonupload;
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\models\SFAccountPreferences.java:	public void setEnableSelfNotificationsUpload(Boolean enableselfnotificationsupload) {
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\models\SFAccountPreferences.java:		this.EnableSelfNotificationsUpload = enableselfnotificationsupload;
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\models\SFAccountPreferences.java:	public void setEnableUploadShareIDReceipt(Boolean enableuploadshareidreceipt) {
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\models\SFAccountPreferences.java:		this.EnableUploadShareIDReceipt = enableuploadshareidreceipt;
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\models\SFAccountPreferences.java:	public void setShowDownloadLinkInUploadNotification(Boolean showdownloadlinkinuploadnotification) {
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\models\SFAccountPreferences.java:		this.ShowDownloadLinkInUploadNotification = showdownloadlinkinuploadnotification;
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\models\SFItemInfo.java:	public void setCanUpload(Boolean canupload) {
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\models\SFItemInfo.java:		this.CanUpload = canupload;
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\models\SFOutlookInformation.java:	public void setUploadInfoLevel(SFOutlookInformationOptionString uploadinfolevel) {
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\models\SFOutlookInformation.java:		this.UploadInfoLevel = uploadinfolevel;
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\models\SFOutlookInformation.java:	public void setNotifyOnUpload(SFOutlookInformationOptionBool notifyonupload) {
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\models\SFOutlookInformation.java:		this.NotifyOnUpload = notifyonupload;
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\models\SFShareRequestParams.java:	public void setNotifyOnUpload(Boolean notifyonupload) {
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\models\SFShareRequestParams.java:		this.NotifyOnUpload = notifyonupload;
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\models\SFUploadSpecification.java:		* The Upload method that must be used for this upload
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\models\SFUploadSpecification.java:		* The Upload method that must be used for this upload
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\models\SFUploadSpecification.java:		* If provided, clients must issue a request to this Uri before uploading any data.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\models\SFUploadSpecification.java:		* If provided, clients must issue a request to this Uri before uploading any data.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\models\SFUploadSpecification.java:		* If provided, specifies the final call the client must perform to finish the upload process
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\models\SFUploadSpecification.java:		* If provided, specifies the final call the client must perform to finish the upload process
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\models\SFUploadSpecification.java:		* Allows the client to check progress of standard uploads
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\models\SFUploadSpecification.java:		* Allows the client to check progress of standard uploads
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\models\SFUploadSpecification.java:		* Specifies a Resumable upload is supproted.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\models\SFUploadSpecification.java:		* Specifies a Resumable upload is supproted.
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\models\SFUserPreferences.java:	public void setEnableFlashUpload(Boolean enableflashupload) {
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\models\SFUserPreferences.java:		this.EnableFlashUpload = enableflashupload;
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\models\SFUserPreferences.java:	public void setEnableJavaUpload(Boolean enablejavaupload) {
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\models\SFUserPreferences.java:		this.EnableJavaUpload = enablejavaupload;
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\models\SFUserPreferences.java:	public void setNotifyOnUploadByDefault(Boolean notifyonuploadbydefault) {
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\models\SFUserPreferences.java:		this.NotifyOnUploadByDefault = notifyonuploadbydefault;
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\SFApiClient.java:    public SFUploadRunnable getUploader(SFUploadRequestParams uploadRequestParams,
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\SFApiClient.java:        return new SFUploadRunnable(uploadRequestParams.geturl().toString(), true,
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\SFApiClient.java:                uploadRequestParams.getFileSize(),
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\SFApiClient.java:                uploadRequestParams.getFileName(),
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\SFApiClient.java:                null, null, uploadRequestParams.getDetails());
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\SFApiClient.java:     * prepare runnable to be used to upload a file
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\SFProvider.java:	 *  "https://szqatest2.sharefiletest.com/sp/upload-streaming-2.aspx?uploadid=rsu-27564a05c0cf4052989099f3e880afda&parentid
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\SFProvider.java:        if(path == null || path.length() < 2 ) //we check this since the path should always contain /v3/ or /upload-streaming
sharefile-api-3.1.2-sources\com\citrix\sharefile\api\utils\Utils.java:		//Don't break the URI in components. On a certain ZK zones we are getting h-params during upload.
ShareFileV3SampleSE.java:	 * Uploads a File using the Standard upload method with a multipart/form mime encoded POST.
ShareFileV3SampleSE.java:	 * @param parentId - where to upload the File
ShareFileV3SampleSE.java:	 * @param localPath - the path of the file to upload, like "c:\\path\\to\\file.name"
ShareFileV3SampleSE.java:	public static void uploadFile(OAuth2Token token, String parentId, String localPath)
ShareFileV3SampleSE.java:			JsonObject uploadConfig = (JsonObject)parser.parse(response.toString());
ShareFileV3SampleSE.java:			JsonElement element = uploadConfig.get("ChunkUri");
ShareFileV3SampleSE.java:	private static void multipartUploadFile(String localPath, String uploadUrl)
ShareFileV3SampleSE.java:		URL url = new URL(uploadUrl);
