Difference: 0LASubrClientUploadFile (2 vs. 3)

Revision 32012-02-02 - JeanNeron

Line: 1 to 1
 
META TOPICPARENT name="APPXRuntimeSubroutineAPI"

.CLIENT UPLOAD FILE

Line: 27 to 27
  <dest_file> is the path and file name on the Appx server the <source_file> should be transferred to (Required). This must be in a location writeable by user 'appx' (Linux/Unix) or the current user (Windows).
Changed:
<
<
<convert_flag> indicates if any file conversion is required (Optional). If zero or not passed, then no conversion will be done. A value of 1 means convert the file automatically based on the filename extension. A value of 2 means convert the file automatically based on the contents of the file (ie, it won't convert binary files). A value of 3 means do the conversion regardless of file type.
>
>
<convert_flag> indicates if any file conversion is required (Optional). The allowable values are:

  • NO - no conversion will be done. This is the default if not PASSed.
  • AUTO-EXT - convert the file automatically based on the filename extension.
  • AUTO-CONTENT - convert the file automatically based on the contents of the file (ie, it won't convert binary files).
  • YES - Do the conversion regardless of file type.
  If conversion is requested, this routine will upload the file to a temporary location, then copy it to the final location, converting as necessary. The temporary copy will be deleted. The temporary copy is created in the applications 'Tmpdata' folder, same as the working files for a restructure.
Line: 49 to 55
 
  • .txt
Changed:
<
<
If a <convert_flag> of 2 is passed, the routine will read approximately the first 1000 bytes of the file and look for characters in the range ASCII 0 to 9 (0x00 to 0x09), or ASCII 14 to 31 (0x0e to 0x1f). If any are found, the file is assumed to be binary and no conversion will take place.
>
>
If a <convert_flag> of AUTO-CONTENT is passed, the routine will read approximately the first 1000 bytes of the file and look for characters in the range ASCII 0 to 9 (0x00 to 0x09), or ASCII 14 to 31 (0x0e to 0x1f). If any are found, the file is assumed to be binary and no conversion will take place.
  If the file is determined to be a text file (either by extension or the lack of binary characters), the routine looks for the presense of a CR/LF pair in the first ~1000 characters of the source file to determine if it's in Unix or Windows format and then uses the following matrix to decide if the file really needs to be converted:
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2021 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback