@ibm-aspera/sdk 0.20.0 → 0.21.0

package/dist/commonjs/app/core.js

@@ -1440,11 +1440,11 @@ var supportsMethod = function (method) {
     // We currently do not support calculating file checksums when using HTTP Gateway. In theory it should be possible
     // to calculate this directly in the browser similar to how `readAsArrayBuffer()` is implemented.
     // HTTP Gateway also does not support showing native transfer client UI (about, preferences, etc.).
-    if (index_1.asperaSdk.useHttpGateway && (method === 'get_checksum' || method === 'show_about' || method === 'open_preferences' || method === 'show_transfer_manager' || method === 'show_transfer_monitor' || method === 'authenticate' || method === 'test_ssh_ports' || method === 'show_save_file_dialog' || method === 'read_directory')) {
+    if (index_1.asperaSdk.useHttpGateway && (method === 'get_checksum' || method === 'show_about' || method === 'open_preferences' || method === 'show_transfer_manager' || method === 'show_transfer_monitor' || method === 'authenticate' || method === 'test_ssh_ports' || method === 'show_save_file_dialog' || method === 'read_directory' || method === 'get_files_list' || method === 'update_branding' || method === 'show_directory' || method === 'modify_transfer' || method === 'resume_transfer')) {
         return false;
     }
     // Reading directory contents is only supported by the Desktop App (not Connect).
-    if (index_1.asperaSdk.useConnect && method === 'read_directory') {
+    if (index_1.asperaSdk.useConnect && (method === 'read_directory' || method === 'get_files_list' || method === 'update_branding')) {
         return false;
     }
     // HTTP Gateway and Connect do not have any RPC methods so fallback to true
@@ -1486,6 +1486,12 @@ var getCapabilities = function () {
         testSshPorts: supportsMethod('test_ssh_ports'),
         showSaveFileDialog: supportsMethod('show_save_file_dialog'),
         readDirectory: supportsMethod('read_directory'),
+        getFilesList: supportsMethod('get_files_list'),
+        setBranding: supportsMethod('update_branding'),
+        showDirectory: supportsMethod('show_directory'),
+        folderUpload: !index_1.asperaSdk.useOldHttpGateway,
+        modifyTransfer: supportsMethod('modify_transfer'),
+        resumeTransfer: supportsMethod('resume_transfer'),
     };
 };
 exports.getCapabilities = getCapabilities;

package/dist/commonjs/http-gateway/core.js

@@ -304,7 +304,8 @@ var getSdkTransfer = function (transferSpec) {
         },
         end_time: '',
         explorer_path: '',
-        status: 'queued',
+        previous_status: 'initiating',
+        status: 'initiating',
         bytes_written: 0,
         bytes_expected: 0,
         calculated_rate_kbps: 0,

package/dist/commonjs/models/aspera-sdk.model.js

@@ -124,10 +124,24 @@ var ActivityTracking = /** @class */ (function () {
      * @param webSocketEvent the event type.
      */
     ActivityTracking.prototype.handleWebSocketEvents = function (webSocketEvent) {
+        var current_status = status_1.statusService.getStatus();
         if (webSocketEvent === 'CLOSED') {
             status_1.statusService.setStatus('DISCONNECTED');
+            return;
+        }
+        if (webSocketEvent !== 'RECONNECT') {
+            return;
         }
-        else if (webSocketEvent === 'RECONNECT') {
+        // Only treat RECONNECT as a transition to RUNNING when we have prior verification of
+        // IBM Aspera for desktop. For example, if IBM Aspera for desktop was RUNNING and verified,
+        // and then the user quits and restarts the application.
+        //
+        // TODO: This potentially leads to a data race if the application was quit/restarted because it was being
+        // upgraded. The new application may have newer RPC methods, but transitioning to RUNNING here could
+        // potentially lead to an application seeing stale RPC methods if they call `hasCapability()`, for example,
+        // in the status event listener.
+        var wasPreviouslyVerified = index_1.asperaSdk.globals.rpcMethods.length > 0;
+        if (current_status === 'DISCONNECTED' || (current_status === 'DEGRADED' && wasPreviouslyVerified)) {
             status_1.statusService.setStatus('RUNNING');
         }
     };

package/dist/commonjs/models/models.d.ts

@@ -663,6 +663,8 @@ export interface AsperaSdkTransfer {
     explorer_path: string;
     /** The status of the transfer */
     status: TransferStatus;
+    /** The previous status of the transfer */
+    previous_status: TransferStatus;
     /** The transfer error description if the status is error */
     error_desc?: string;
     /** The transfer error code (SSH or HTTP) if the status is error */
@@ -964,70 +966,99 @@ export interface RpcMethod {
  */
 export interface SdkCapabilities {
     /**
-     * Whether the SDK can read file contents for generating image previews.
+     * Whether the transfer client can read file contents for generating image previews.
      *
-     * Image preview is supported if the SDK is using HTTP Gateway, Connect, or IBM Aspera for desktop
-     * with the required RPC methods.
+     * This is supported when using HTTP Gateway, Connect, or IBM Aspera for desktop.
     */
     imagePreview: boolean;
     /**
-     * Whether the SDK can calculate checksums of a file chunk.
+     * Whether the transfer client can calculate checksums of a file chunk.
      */
     fileChecksum: boolean;
     /**
      * Whether the transfer client supports showing the about page.
      *
-     * This is supported when using Connect or IBM Aspera for desktop with the required RPC methods,
-     * but not HTTP Gateway.
+     * This is supported when using Connect or IBM Aspera for desktop.
      */
     showAbout: boolean;
     /**
      * Whether the transfer client supports showing the preferences page.
      *
-     * This is supported when using Connect or IBM Aspera for desktop with the required RPC methods,
-     * but not HTTP Gateway.
+     * This is supported when using Connect or IBM Aspera for desktop.
      */
     showPreferences: boolean;
     /**
      * Whether the transfer client supports showing the transfer manager.
      *
-     * This is supported when using Connect or IBM Aspera for desktop with the required RPC methods,
-     * but not HTTP Gateway.
+     * This is supported when using Connect or IBM Aspera for desktop.
      */
     showTransferManager: boolean;
     /**
      * Whether the transfer client supports showing the transfer rate monitor.
      *
-     * This is supported when using Connect or IBM Aspera for desktop with the required RPC methods,
-     * but not HTTP Gateway.
+     * This is supported when using Connect or IBM Aspera for desktop.
      */
     showTransferMonitor: boolean;
     /**
      * Whether the transfer client supports authenticating a transfer specification.
      *
-     * This is supported when using Connect or IBM Aspera for desktop with the required RPC methods,
-     * but not HTTP Gateway.
+     * This is supported when using Connect or IBM Aspera for desktop.
      */
     authenticate: boolean;
     /**
      * Whether the transfer client supports testing SSH port connectivity.
      *
-     * This is supported when using Connect or IBM Aspera for desktop with the required RPC methods,
-     * but not HTTP Gateway.
+     * This is supported when using Connect or IBM Aspera for desktop.
      */
     testSshPorts: boolean;
     /**
      * Whether the transfer client supports showing the save file dialog.
      *
-     * This is supported when using Connect or IBM Aspera for desktop with the required RPC methods,
-     * but not HTTP Gateway.
+     * This is supported when using Connect or IBM Aspera for desktop.
      */
     showSaveFileDialog: boolean;
     /**
-     * Whether the SDK can read directory contents.
+     * Whether the transfer client can read directory contents.
      *
-     * This is supported when using IBM Aspera for desktop with the required RPC methods,
-     * but not Connect or HTTP Gateway.
+     * This is only supported when using IBM Aspera for desktop.
      */
     readDirectory: boolean;
+    /**
+     * Whether the transfer client supports getting file-level progress for a given transfer.
+     *
+     * This is supported when using IBM Aspera for desktop.
+     */
+    getFilesList: boolean;
+    /**
+     * Whether the transfer client supports customized branding settings.
+     *
+     * This is supported when using IBM Aspera for desktop.
+     */
+    setBranding: boolean;
+    /**
+     * Whether the transfer client supports highlighting the destination directory of the transfer
+     * using the system's file browser (ex: Finder or Windows Explorer).
+     *
+     * This is supported when using Connect or IBM Aspera for desktop.
+     */
+    showDirectory: boolean;
+    /**
+     * Whether the transfer client supports uploading folders.
+     *
+     * This is supported when using Connect, IBM Aspera for desktop, and HTTP Gateway v3 or newer. HTTP Gateway v2 and older
+     * do not support uploading folders.
+     */
+    folderUpload: boolean;
+    /**
+     * Whether the transfer client can modify a running transfer.
+     *
+     * This is supported when using Connect or IBM Aspera for desktop.
+     */
+    modifyTransfer: boolean;
+    /**
+     * Whether the transfer client resume a stopped transfer.
+     *
+     * This is supported when using Connect or IBM Aspera for desktop.
+     */
+    resumeTransfer: boolean;
 }